CVE-2026-126129: Auth0 ASP.NET Core Authentication · Reliance on Untrusted Inputs in a Security Decision
Affects Auth0 ASP.NET Core AuthenticationSource CVE Database V5
Not known to be exploited : upgrade to 1.12.0 soon.
Data as of 10 Nov 2026, 21:35 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.12.0
Exploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade Auth0 ASP.NET Core Authentication to 1.12.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Auth0Auth0 ASP.NET Core Authentication | Affected
| Fixed in
|
AI-suggested
Upgrade to Auth0 ASP.NET Core Authentication SDK version 1.12.0 or later, where this vulnerability has been fixed. No other mitigation is indicated by the vendor advisory.
Description
CVE-2026-126129 is a vulnerability in the Auth0 ASP.NET Core Authentication SDK where the session's OIDC Back-Channel Logout status is incorrectly determined. This flaw may allow a session that has been logged out to still be accepted for access to protected endpoints. The issue affects versions prior to 1.12.0 and has been fixed in version 1.12.0.