Skip to content
Web

CVE-2026-49757

9.2
Critical
EPSS 0.61%Patch availableJun 15, 2026

OAuth/OIDC auth bypass enables local account takeover via email identity.

common questions

Is CVE-2026-49757 being exploited?

Not confirmed. CVE-2026-49757 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.61% probability of exploitation in the next 30 days.

How severe is CVE-2026-49757?

CVE-2026-49757 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-49757?

Yes. A fix has been recorded for CVE-2026-49757. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-49757 affect?

CVE-2026-49757 affects ash_authentication (versions < 4.14.0, <5.0.0-rc.10). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-49757?

Upgrade to ash_authentication >= 4.14.0 or 5.0.0-rc.10

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ash_authentication (versions < 4.14.0, <5.0.0-rc.10)
impact

Unauthenticated attacker can take over a victim's local account by using the victim's email in OAuth/OIDC sign-in (email not a stable id).

action required

Immediate action required

affected versions
team-alembic ash_authentication
  • affected>= 0.1.0 and < 4.14.0
  • affected>= 5.0.0-rc.0 and < 5.0.0-rc.10
  • affected>= c5f589058e04239263f50a1430eb17ea6d5dd1a2 and < *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free