CVE-2026-123871: Proxy credential disclosure in Node.js configuration errors
Node.js 22.x, 24.x, and 26.x disclose proxy usernames and passwords through four error paths that interpolate an unredacted, environment-supplied proxy URL into ERR_PROXY_INVALID_CONFIG messages. These paths, including one in the ProxyConfig constructor, were missed by the CVE-2026-48615 fix, which redacted credentials from ProxyConfig.href. Resulting error messages can propagate secrets to stderr, container logs, log aggregation systems, and crash reporting services.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Proxy credentials can become accessible to users or services that can read application errors or downstream telemetry but cannot access the process environment. This creates a confidentiality breach and may enable unauthorized use of the affected proxy where the disclosed credentials remain valid. No direct integrity or availability impact is identified.
Mitigation
If you can’t patch tonight, do this now.
Until patched, validate credential-bearing proxy configuration before it reaches the affected error paths, restrict access to stderr and downstream logging or crash-reporting systems, and redact proxy credentials before exporting error messages. These measures reduce exposure but do not correct Node.js error generation. Rotate proxy credentials if they have already appeared in errors or telemetry.
Remediation
Patch, then assume compromise.
Upgrade to Node.js 22.23.5, 24.22.3, or 26.13.1, or a later patched release in the applicable branch. The fix redacts proxy credentials from invalid proxy URL errors. For Alpine Linux, update the relevant packages to 22.23.5-r0 or 24.22.3-r0 or later. Distribution patch availability varies; where the installed package will not receive a fix, migrate to a patched runtime.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-123871 exploited in the wild?
- As of Nov 16, 2026, Mallory has no reports of CVE-2026-123871 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-123871?
- As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-123871.
- Is there a patch for CVE-2026-123871?
- Upgrade to Node.js 22.23.5, 24.22.3, or 26.13.1, or a later patched release in the applicable branch. The fix redacts proxy credentials from invalid proxy URL errors.
- How severe is CVE-2026-123871?
- CVE-2026-123871 has a CVSS v3 score of 6.2 (Medium) and an EPSS score of 0.17% (7th percentile) as of Nov 16, 2026.
Recent activity
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.