WhatBrokeToday
GTA 6FAQ
Node.js

Auth0 Node.js SDK Management API Client Improperly Neutralizes Path Parameters

high

Is it fixed? Not yet.

Ongoing since Nov 10, 21:19 UTC. First reported Nov 10, 21:19 UTC.

What happened

A high severity vulnerability (CVE-2026-126128) exists in the Management API client of the Auth0 Node.js SDK where path parameters are improperly neutralized. This allows requests and attached management API tokens to be redirected to unintended endpoints on the same tenant, potentially exposing data or operations permitted by the token's existing scopes.

What caused it?

The Management API client in the Auth0 Node.js SDK improperly neutralizes path parameters, causing requests and tokens to be redirected to unintended endpoints.

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on security advisory

    Management API client in the Auth0 Node.js SDK improperly neutralizes path parameters, allowing a request and its at: CVE-2026-126128 (High)

    Source

Evidence

1 report · 1 CVEShow
  1. [1]
    CVE First report
    Management API client in the Auth0 Node.js SDK improperly neutralizes path parameters, allowing a request and its at: CVE-2026-126128 (High)(opens security advisory in a new tab)

    High severity. 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.

    by Tenable 0upvotes 0comments

FAQ

What happened in the Node.js issue?

A high severity vulnerability (CVE-2026-126128) exists in the Management API client of the Auth0 Node.js SDK where path parameters are improperly neutralized. This allows requests and attached management API tokens to be redirected to unintended endpoints on the same tenant, potentially exposing data or operations permitted by the token's existing scopes.

What is affected by the Node.js issue?

Node.js.

When did the Node.js issue start and end?

It started Nov 10, 21:19 UTC and is still ongoing (8 d 7 h so far). This page updates as it develops.

How do I get alerts for Node.js?

Subscribe to the Node.js RSS feed for every new Node.js incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Node.js is down. Node.js feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.