CVE-2026-49757

OAuth2/OIDC account takeover in AshAuthentication via email-based user matching

State
Published
Severity
9.2 Critical
Published
Jun 15, 2026
Updated
Jun 15, 2026
Reserved
Jun 1, 2026

Read the record on cve.org

Description

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.1.0 before 4.14.0 and from 5.0.0-rc.0 before 5.0.0-rc.10.

Scores

CVSSScoreVectorSource
4.09.2 CriticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NEEF

Weaknesses

  • CWE-290 Authentication Bypass by Spoofing

Affected Products

ProductVersions
ash_authenticationteam-alembic
  • 0.1.0 to before 4.14.0Affected
  • 5.0.0-rc.0 to before 5.0.0-rc.10Affected
ash_authenticationteam-alembic
  • c5f589058e04239263f50a1430eb17ea6d5dd1a2 and laterAffectedfrom 728b8d28c1b5f465fa1116ef044a815300fc733dNot affectedfrom 64530644f9b37ebb76ca14aeb83a77597a0034b7Not affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.