How many CVEs have patched email_matches_account?

1 published CVEs changed email_matches_account in team-alembic/ash_authentication, in 2 distinct patches totalling 9 changed lines, between 2026 and 2026.

What is the latest CVE that changed email_matches_account?

CVE-2026-88952 (OAuth2 sign-in attached to an existing account without an email comparison in AshAuthentication), published 2026-09-17, changed lines 220 to 228 of lib/ash_authentication/strategies/oauth2/user_resolver.ex.

How does email_matches_account compare to the rest of team-alembic/ash_authentication?

team-alembic/ash_authentication has 20 CVEs with a located fix in total; 1 of them changed email_matches_account.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Team Alembic
Ash_authentication
Email_matches_account

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Team Alembic
Ash_authentication
Email_matches_account

email_matches_account in team-alembic/ash_authentication: Patched by 1 CVEs

team-alembic/ash_authentication

Function

email_matches_account

Name: email_matches_account in team-alembic/ash_authentication: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

lib/ash_authentication/strategies/oauth2/user_resolver.ex

Last patched September 17, 2026

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

email_matches_account in team-alembic/ash_authentication was changed by 1 published CVE fixes in 2026, in 2 distinct patches that added or removed 9 lines in total.

team-alembic/ash_authentication has 20 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed email_matches_account, newest first, with the lines each fix touched.

OAuth2 sign-in attached to an existing account without an email comparison in AshAuthentication
CVE-2026-88952 · lines 220–228 · +9 −0
Critical · CVSS 9.1
EPSS 0.7%2026-09-17

Get an alert when the next CVE fix lands in team-alembic/ash_authentication, with the patched functions.

Monitor ash_authentication CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1Otherwiselib/ash_authentication/strategies/oauth2/user_resolver.ex3 CVEs · 3 patches2026

Other hotspots in the repository

Functions in team-alembic/ash_authentication changed by the most CVE fixes.

Otherwise3 CVEs · lib/ash_authentication/strategies/oauth2/user_resolver.ex uid_from_user_info3 CVEs · lib/ash_authentication/strategies/oauth2.ex do_change3 CVEs · lib/ash_authentication/strategies/oauth2/identity_change.ex map_join3 CVEs · lib/mix/tasks/ash_authentication.add_strategy.ex store_identity_link3 CVEs · lib/ash_authentication/add_ons/confirmation/actions.ex verify3 CVEs · lib/ash_authentication/strategies/apple/verifier.ex

All patched functions in team-alembic/ash_authentication

Frequently asked questions

Common questions about CVE fixes to email_matches_account.

How many CVEs have patched email_matches_account?: 1 published CVEs changed email_matches_account in team-alembic/ash_authentication, in 2 distinct patches totalling 9 changed lines, between 2026 and 2026.
What is the latest CVE that changed email_matches_account?: CVE-2026-88952 (OAuth2 sign-in attached to an existing account without an email comparison in AshAuthentication), published 2026-09-17, changed lines 220 to 228 of lib/ash_authentication/strategies/oauth2/user_resolver.ex.
How does email_matches_account compare to the rest of team-alembic/ash_authentication?: team-alembic/ash_authentication has 20 CVEs with a located fix in total; 1 of them changed email_matches_account.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

lib/ash_authentication/strategies/oauth2/user_resolver.ex on GitHub (opens in a new tab)
All patched functions in team-alembic/ash_authentication
Patched functions directory

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track team-alembic/ash_authentication CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing

On this page

Overview
CVEs that patched it
Other functions in these files
Other hotspots in the repository
FAQ
References