Node.js is vulnerable to proxy credential disclosure via ERR_PROXY_INVALID_CONFIG error messages
cve-program · CVE-2026-123871
PublishedNode.js discloses proxy credentials in ERR_PROXY_INVALID_CONFIG error messages. CVE-2026-48615 established that a proxy credential must not appear in a Node.js error message and redacted the username and password from ProxyConfig.href, but that fix missed four error paths in the same subsystem, one of them inside the same constructor, which interpolate the raw proxy URL, credentials included, into an ERR_PROXY_INVALID_CONFIG message. The proxy URL comes from the environment, but the defect is the sink: a secret that Node.js redacts everywhere else is emitted verbatim into a much wider audience than the process environment, such as stderr, container logs, log aggregation, and crash reporting services. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-123871 · CVE overview and exploitation status
cve-program · CVE-2026-123871
Related changes
Linked by CVE identifier- Node.js is vulnerable to proxy credential disclosure via ERR_PROXY_INVALID_CONFIG error messages · Newly collected advisory · 11 Nov 2026
- Wednesday, November 11, 2026 Security Releases · Security advisory · 11 Nov 2026