CVE-2026-123871: Node.js is vulnerable to proxy credential disclosure via ERR_PROXY_INVALID_CONFIG error messages
nodejs · node
Vendor fix available · Affected: nodejs · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 5% of scored CVEs
DescriptionCVE.org
Node.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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- nodejs · nodefrom 0.0.0 before 22.23.5; from 23.0.0 before 24.22.3; from 25.0.0 before 26.13.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- nodejs
- Published
- November 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-123871 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.