Skip to main content
cve.nowby Sazabi
← Vulnerabilities
CVE-2026-126129EUVD-2026-122940

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

Exploited
No known exploitation
Fix
Fixed in 1.12.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.12.0.

Published
Last modified
Reference
Last checked
0/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The Auth0 ASP.NET Core Authentication SDK incorrectly determines whether a session has been ended through OIDC Back-Channel Logout, which can allow a logged-out session to still be accepted for access to protected endpoints. No CVSS vector or advisory impact data is provided, so how an attacker reaches the flaw is not specified here.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

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.

cve.now Index

0Pcve.now Index 0 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 55 if added to CISA KEV
  • Would score about 50 if CISA's SSVC rates exploitation active
  • Would score about 22 if advisories confirm default setups are exposed

How the score works · Rankings

What to do

  • Upgrade to a fixed version: 1.12.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126129 (The Auth0 ASP.NET Core Authentication SDK incorrectly determines a session's OIDC Back-Channel Logout status, which may result in a…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126129 (entry last updated 2026-11-10):
Affected:
- Auth0 Auth0 ASP.NET Core Authentication: fixed in 1.12.0
Fixed versions: 1.12.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126129 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126129 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://trust.okta.com/security-advisories/improper-backchannel-session-revocation-in-the-auth0-asp-net-core-authentication-sdk-cve-2026-126129
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126129
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-126129.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Auth0 Auth0 ASP.NET Core Authentication

    fixed in 1.12.0

Evidence 3

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126129

Is CVE-2026-126129 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-126129?

Auth0 ASP.NET Core Authentication: before 1.12.0.Source: cve.now feed data

How do I fix CVE-2026-126129?

Upgrade to a fixed version: 1.12.0.Source: cve.now feed data

Sources

Related

More vulnerabilities