The Auth0 ASP.NET Core Authentication SDK incorrectly determines a session's OIDC Back-Channel Logout status, which may result in a logged-…

published 2026-11-10 yesterday modified 2026-11-10 yesterday also EUVD-2026-122940

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits: 0; none known

The Auth0 ASP.NET Core Authentication SDK incorrectly determines a session's OIDC Back-Channel Logout status, which may result in a logged-out session being accepted for access to protected endpoints.

Patch / fix

fixed in 1

Auth0 Auth0 ASP.NET Core Authentication 1.12.0

Is CVE-2026-126129 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-11).

Affected products

Auth0 Auth0 ASP.NET Core Authentication

Classification

Weakness

CWE-807 Reliance on Untrusted Inputs in a Security Decision
CWE-287 Improper Authentication
CWE-1254 Incorrect Comparison Logic Granularity

References

trust.okta.com /security-advisories/improper-backchannel-session-revocation-in-the-auth0-asp-net-core-authentication-sdk-cve-

Sources

CVE List CVE-2026-126129
NVD CVE-2026-126129

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.