CVSS 3.0
6.2 mediumCVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVE-2026-123871 Node.js is vulnerable to proxy credential disclosure via ERR_PROXY_INVALID_CONFIG error messages
Medium (6.2) in nodejs node. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-209 Generation of Error Message Containing Sensitive Information
- OWASP Top 10
- A10:2025 Mishandling of Exceptional Conditions
- Published
- Modified
- Assigned by
- openjs (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123871 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123871?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123871?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123871 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-123871)
HTML:
<a href="https://cve.bz/cve/CVE-2026-123871"><img src="https://cve.bz/cve/badge/CVE-2026-123871.svg" alt="CVE-2026-123871"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| nodejs node | from 0.0.0 before 22.23.5 |
| nodejs node | from 23.0.0 before 24.22.3 |
| nodejs node | from 25.0.0 before 26.13.1 |
Fix and patched versions
- Red Hat, Alpine, Alpaquita, BellSoft Hardened Containers: fixed package versions per release
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | nodejs | no fix listed | DEBIAN-CVE-2026-123871 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 and 5 more | nodejs | no fix listed | UBUNTU-CVE-2026-123871 |
| Red Hat | hummingbird:1 | nodejs22, nodejs22-bin, nodejs22-docs and 4 more | 1:22.23.5-2.3.2.3.1.hum1 | RHSA-2026:99433 |
| Red Hat | hummingbird:1 | nodejs22-npm | 1:10.9.9-1.22.23.5.2.3.2.3.1.hum1 | RHSA-2026:99433 |
| Red Hat | hummingbird:1 | nodejs24, nodejs24-bin, nodejs24-docs and 3 more | 1:24.22.3-0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs24-npm | 2:11.19.1-1.24.22.3.0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs24-npm-bin | 2:24.22.3-0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs26, nodejs26-bin, nodejs26-docs and 4 more | 1:26.13.1-0.1.hum1 | RHSA-2026:99436 |
| Red Hat | hummingbird:1 | nodejs26-npm | 1:11.20.0-1.26.13.1.0.1.hum1 | RHSA-2026:99436 |
| Alpine | v3.21, v3.22 | nodejs | 22.23.5-r0 | ALPINE-CVE-2026-123871 |
| Alpine | v3.23, v3.24 | nodejs | 24.22.3-r0 | ALPINE-CVE-2026-123871 |
| Alpine | v3.24 | nodejs-current | 26.13.1-r0 | ALPINE-CVE-2026-123871 |
| Alpaquita | stream | nodejs22 | 22.23.5-r0 | BELL-CVE-2026-123871 |
| Alpaquita | stream | nodejs24 | 24.22.3-r0 | BELL-CVE-2026-123871 |
| Alpaquita | stream | nodejs26 | 26.13.1-r0 | BELL-CVE-2026-123871 |
| BellSoft Hardened Containers | stream | nodejs22 | 22.23.5-r0 | BELL-CVE-2026-123871 |
| BellSoft Hardened Containers | stream | nodejs24 | 24.22.3-r0 | BELL-CVE-2026-123871 |
| BellSoft Hardened Containers | stream | nodejs26 | 26.13.1-r0 | BELL-CVE-2026-123871 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpine · Alpaquita · BellSoft Hardened Containers.
Red Hat
Red Hat rates this Moderate.
This vulnerability is rated as Moderate impact because sensitive proxy authentication credentials may be exposed to unauthorized observers through application output channels, yet exploitation does not grant direct system compromise or remote code execution. In typical Red Hat Enterprise Linux and OpenShift container deployments, Node.js applications configured with erroneous proxy settings can print intact secrets into standard error streams, shared container logs, or log collectors. Exposure is limited to environments where proxy authentication is configured and specific configuration errors occur during proxy initialization.
Avoid placing proxy credentials in the environment of long-lived services; prefer credential helpers or secret stores. Restrict access to logs that may capture ERR_PROXY_INVALID_CONFIG messages.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | nodejs22 | Fix deferred | |
| Red Hat Enterprise Linux 10 | nodejs24 | Fix deferred | |
| Red Hat Enterprise Linux 10 | nodejs26 | Fix deferred | |
| Red Hat Enterprise Linux 8 | nodejs:22/nodejs | Fix deferred | |
| Red Hat Enterprise Linux 8 | nodejs:24/nodejs | Fix deferred | |
| Red Hat Enterprise Linux 9 | nodejs:22/nodejs | Fix deferred | |
| Red Hat Enterprise Linux 9 | nodejs:24/nodejs | Fix deferred | |
| Red Hat Enterprise Linux 9 | nodejs:26/nodejs | Fix deferred | |
| Red Hat Hardened Images | hi/nodejs | Under investigation | |
| Red Hat Hardened Images | nodejs20 | Will not fix | |
| Red Hat Hardened Images | nodejs22 | Affected | |
| Red Hat Hardened Images | nodejs24 | Affected | |
| Red Hat Hardened Images | nodejs25 | Will not fix | |
| Red Hat Hardened Images | nodejs26 | Affected | |
| Red Hat Hardened Images | npm12 | Under investigation |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-123871.
Attack patterns (CAPEC)
- CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
- CAPEC-54 Query System for Information Likelihood: High · Severity: Low
- CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low
- CAPEC-463 Padding Oracle Crypto Attack Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.