CVE
Node.js is vulnerable to proxy credential disclosure via ERR_PROXY_INVALID_CONFIG error messages
- Exploited
- No known exploitation
- Fix
- Fixed in 22.23.5, 24.22.3, 26.13.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 22.23.5, 24.22.3, 26.13.1.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 23/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Node.js (nodejs/node) is affected: when a proxy is misconfigured, its ERR_PROXY_INVALID_CONFIG error messages can print the proxy URL with its username and password in plain text. An attacker with local access, and no login needed, can read those credentials from places such as stderr, container logs, or crash reports, where a process's proxy error message is recorded.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach17/20Affects Node.js (a widely deployed server, runtime, framework or database)
- Severity6.2/10CVSS 6.2
- No patch0/5No signal
What would change the score
- Would score about 78 if added to CISA KEV
- Would score about 73 if CISA's SSVC rates exploitation active
- Would score about 45 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 22.23.5, 24.22.3, 26.13.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-123871 (Node.js is vulnerable to proxy credential disclosure via ERR_PROXY_INVALID_CONFIG error messages), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-123871 (entry last updated 2026-11-11):
Affected:
- nodejs node: from 0.0.0, fixed in 22.23.5; from 23.0.0, fixed in 24.22.3; from 25.0.0, fixed in 26.13.1
Fixed versions: 22.23.5, 24.22.3, 26.13.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123871 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123871 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://nodejs.org/en/blog/vulnerability/november-2026-security-releases
- https://cna.openjsf.org/security-advisories.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-123871
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123871"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- nodejs node
From 0.0.0 · fixed in 22.23.5; From 23.0.0 · fixed in 24.22.3; From 25.0.0 · fixed in 26.13.1
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123871
Is CVE-2026-123871 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123871?
node: from 0.0.0 before 22.23.5; from 23.0.0 before 24.22.3; from 25.0.0 before 26.13.1.Source: cve.now feed data
How do I fix CVE-2026-123871?
Upgrade to a fixed version: 22.23.5, 24.22.3, 26.13.1.Source: cve.now feed data