Answer in brief
CVE-2026-49757 records a Critical severity (CVSS 9.2) vulnerability in OAuth2/OIDC account takeover in AshAuthentication via email-based user matching. The current sources do not mark it as known exploited. The current feed maps ash_authentication (erlang), ash_authentication (erlang), team-alembic/ash_authentication (generic), team-alembic/team-alembic/ash_authentication (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ash_authentication (erlang), ash_authentication (erlang), team-alembic/ash_authentication (generic), team-alembic/team-alembic/ash_authentication (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash_authenticationerlang | >=0.1.0,<4.14.0 | 4.14.0 |
| ash_authenticationerlang | >=5.0.0-rc.0,<5.0.0-rc.10 | 5.0.0-rc.10 |
| team-alembic/ash_authenticationgeneric | >=0.6.0 <4.14.0 || >=5.0.0-rc.0 <5.0.0-rc.10 | 4.14.0, 5.0.0-rc.10 |
| team-alembic/team-alembic/ash_authenticationgeneric | >=c5f589058e04239263f50a1430eb17ea6d5dd1a2 <* | * |
Published upstream
Jun 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 25, 2026
Authentication Bypass by Spoofing vulnerability in team-alembic AshAuthentication allows account takeover of local users via OAuth2/OIDC sign-in. AshAuthentication's OAuth2 and OIDC family strategies matched the local user by email address (an upsert on the email field, or a user-defined sign-in filter) rather than by the OpenID Connect iss/sub claim combination. Per OpenID Connect Core §5.7, only iss/sub uniquely and stably identifies an end-user; other claims, including email, MUST NOT be used as unique identifiers. A provider login presenting a victim's email, including an unverified email, a reused email, or an account with email_verified: false, resolved to and signed in as the victim's existing local account. An unauthenticated attacker who can register an account on any accepted OAuth provider with the victim's email (or who benefits from provider-side email reuse or reclamation) obtains the victim's full local privileges. The fix resolves users by the (strategy, sub) identity stored in a user identity resource, and only links a new sub to an existing local account by email when the provider's email_verified claim is trusted (trust_email_verified?). This issue affects ash_authentication: from 0.6.0 before 4.14.0 and from 5.0.0-rc.0 before 5.0.0-rc.10.
Quoted source text, attributed separately from HOL analysis.