CVE-2026-126128 The Management API client in the Auth0 Node.js SDK improperly neutralizes path parameters, allowing a request and its attached management AP
Not scored
Published
Updated
Check this codebase for CVE-2026-126128 and fix it if it is affected.
What it is: CVE-2026-126128 is a vulnerability in Auth0 Node JS, published on 10 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-126128 in the wild and no public exploit code.
Affected product: Auth0 Node JS. 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-126128/ (Markdown: https://insights.sbomify.com/CVE-2026-126128/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-126128?
CVE-2026-126128 is a vulnerability in Auth0 Node JS, published on 10 Nov 2026.
Official description
The Management API client in the Auth0 Node.js SDK improperly neutralizes path parameters, allowing a request and its attached management API token to be redirected to an unintended endpoint on the same tenant, resulting in unintended access to data or operations that the token's existing scopes already permit.
Which versions are affected by CVE-2026-126128?
How do I fix CVE-2026-126128?
No fix has been published for CVE-2026-126128 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-126128 being exploited?
There is no known exploitation of CVE-2026-126128 in the wild and no public exploit code.