CVE-2026-123871: ERR_PROXY_INVALID_CONFIG error messages · Node.js discloses proxy credentials
Source GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.2 Medium · fixed in 26.13.1 : update node when convenient.
Data as of 11 Nov 2026, 22:35 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.0 | 6.2 |
|---|
- Patch
- Available – fixed in 26.13.1, 24.22.3, 22.23.5
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade node to 26.13.1, 24.22.3 or 22.23.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nodejsnode | Affected
| Fixed in
|
| nodejsnode | Affected
| Fixed in
|
| nodejsnode | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, users should avoid exposing error outputs containing proxy configurations or sanitize logs to prevent credential leakage.
Description
Node.js versions 22.x, 24.x, and 26.x disclose proxy credentials in ERR_PROXY_INVALID_CONFIG error messages. This occurs because certain error paths interpolate the raw proxy URL, including sensitive credentials, into error messages that are exposed to stderr, logs, and crash reporting services. The vulnerability results from incomplete redaction of proxy credentials in error outputs.