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 logged-o
Not scored
Published
Updated
Check this codebase for CVE-2026-126129 and fix it if it is affected.
What it is: CVE-2026-126129 is a vulnerability in Auth0 ASP.NET Core Authentication, published on 10 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-126129 in the wild and no public exploit code.
Affected product: Auth0 ASP.NET Core Authentication. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-126129/ (Markdown: https://insights.sbomify.com/CVE-2026-126129/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-126129?
CVE-2026-126129 is a vulnerability in Auth0 ASP.NET Core Authentication, published on 10 Nov 2026.
Official 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.
Which versions are affected by CVE-2026-126129?
How do I fix CVE-2026-126129?
No fix has been published for CVE-2026-126129 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-126129 being exploited?
There is no known exploitation of CVE-2026-126129 in the wild and no public exploit code.