cve.bz

CVE-2026-126128 auth0 auth0 node js: Path traversal

no score yetEPSS 0.2%

auth0 auth0 node js: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-706 Use of Incorrectly-Resolved Name or Reference
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
Okta (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-126128 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126128?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126128?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126128 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126128

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126128](https://cve.bz/cve/badge/CVE-2026-126128.svg)](https://cve.bz/cve/CVE-2026-126128)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126128"><img src="https://cve.bz/cve/badge/CVE-2026-126128.svg" alt="CVE-2026-126128"></a>

Affected

  • auth0:auth0 node js

Versions

From the CNA's record in the CVE List.

ProductAffected
Auth0 Node JSfrom 4.0.0 before 7.6.0

Attack patterns (CAPEC)

  • CAPEC-48 Passing Local Filenames to Functions That Expect a URL Likelihood: High · Severity: High
  • CAPEC-159 Redirect Access to Libraries Likelihood: High · Severity: Very High
  • CAPEC-177 Create files with the same name as files protected with a higher classification Severity: Very High
  • CAPEC-641 DLL Side-Loading Likelihood: Low · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON