UBUNTU-CVE-2026-123871 (CVE-2026-123871)
Vulnerability from osv_ubuntu – Published: 2026-11-12 00:00 – Updated: 2026-11-13 18:04 – Source websiteNode.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": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "nodejs",
"binary_version": "0.10.25~dfsg2-2ubuntu1.2+esm2"
},
{
"binary_name": "nodejs-legacy",
"binary_version": "0.10.25~dfsg2-2ubuntu1.2+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "nodejs",
"purl": "pkg:deb/ubuntu/nodejs@0.10.25~dfsg2-2ubuntu1.2+esm2?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.10.15~dfsg1-4",
"0.10.21~dfsg1-1",
"0.10.22~dfsg1-2",
"0.10.23~dfsg1-1",
"0.10.23~dfsg1-2",
"0.10.23~dfsg1-3",
"0.10.24~dfsg1-1",
"0.10.25~dfsg2-2",
"0.10.25~dfsg2-2ubuntu1",
"0.10.25~dfsg2-2ubuntu1.2",
"0.10.25~dfsg2-2ubuntu1.2+esm1",
"0.10.25~dfsg2-2ubuntu1.2+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "nodejs",
"binary_version": "4.2.6~dfsg-1ubuntu4.2+esm3"
},
{
"binary_name": "nodejs-legacy",
"binary_version": "4.2.6~dfsg-1ubuntu4.2+esm3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "nodejs",
"purl": "pkg:deb/ubuntu/nodejs@4.2.6~dfsg-1ubuntu4.2+esm3?arch=source\u0026distro=esm-apps/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.10.25~dfsg2-2ubuntu1",
"4.2.2~dfsg-1",
"4.2.3~dfsg-1",
"4.2.4~dfsg-1ubuntu1",
"4.2.4~dfsg-2",
"4.2.6~dfsg-1ubuntu1",
"4.2.6~dfsg-1ubuntu4",
"4.2.6~dfsg-1ubuntu4.1",
"4.2.6~dfsg-1ubuntu4.2",
"4.2.6~dfsg-1ubuntu4.2+esm1",
"4.2.6~dfsg-1ubuntu4.2+esm2",
"4.2.6~dfsg-1ubuntu4.2+esm3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "nodejs",
"binary_version": "8.10.0~dfsg-2ubuntu0.4+esm6"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "nodejs",
"purl": "pkg:deb/ubuntu/nodejs@8.10.0~dfsg-2ubuntu0.4+esm6?arch=source\u0026distro=esm-apps/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.11.4~dfsg-1ubuntu1",
"6.11.4~dfsg-1ubuntu2",
"6.12.0~dfsg-1ubuntu1",
"6.12.0~dfsg-2ubuntu1",
"6.12.0~dfsg-2ubuntu2",
"8.10.0~dfsg-2",
"8.10.0~dfsg-2ubuntu0.2",
"8.10.0~dfsg-2ubuntu0.3",
"8.10.0~dfsg-2ubuntu0.4",
"8.10.0~dfsg-2ubuntu0.4+esm1",
"8.10.0~dfsg-2ubuntu0.4+esm2",
"8.10.0~dfsg-2ubuntu0.4+esm3",
"8.10.0~dfsg-2ubuntu0.4+esm4",
"8.10.0~dfsg-2ubuntu0.4+esm5",
"8.10.0~dfsg-2ubuntu0.4+esm6"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnode64",
"binary_version": "10.19.0~dfsg-3ubuntu1.6+esm2"
},
{
"binary_name": "nodejs",
"binary_version": "10.19.0~dfsg-3ubuntu1.6+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "nodejs",
"purl": "pkg:deb/ubuntu/nodejs@10.19.0~dfsg-3ubuntu1.6+esm2?arch=source\u0026distro=esm-apps/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"10.15.2~dfsg-2ubuntu1",
"10.17.0~dfsg-2ubuntu4",
"10.17.0~dfsg-2ubuntu6",
"10.19.0~dfsg-3ubuntu1",
"10.19.0~dfsg-3ubuntu1.1",
"10.19.0~dfsg-3ubuntu1.2",
"10.19.0~dfsg-3ubuntu1.3",
"10.19.0~dfsg-3ubuntu1.5",
"10.19.0~dfsg-3ubuntu1.6",
"10.19.0~dfsg-3ubuntu1.6+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnode72",
"binary_version": "12.22.9~dfsg-1ubuntu3.6+esm2"
},
{
"binary_name": "nodejs",
"binary_version": "12.22.9~dfsg-1ubuntu3.6+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:22.04:LTS",
"name": "nodejs",
"purl": "pkg:deb/ubuntu/nodejs@12.22.9~dfsg-1ubuntu3.6+esm2?arch=source\u0026distro=esm-apps/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"12.22.5~dfsg-5ubuntu1",
"12.22.7~dfsg-2ubuntu1",
"12.22.7~dfsg-2ubuntu3",
"12.22.9~dfsg-1ubuntu2",
"12.22.9~dfsg-1ubuntu3",
"12.22.9~dfsg-1ubuntu3.1",
"12.22.9~dfsg-1ubuntu3.2",
"12.22.9~dfsg-1ubuntu3.3",
"12.22.9~dfsg-1ubuntu3.4",
"12.22.9~dfsg-1ubuntu3.5",
"12.22.9~dfsg-1ubuntu3.6",
"12.22.9~dfsg-1ubuntu3.6+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnode109",
"binary_version": "18.19.1+dfsg-6ubuntu5"
},
{
"binary_name": "nodejs",
"binary_version": "18.19.1+dfsg-6ubuntu5"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "nodejs",
"purl": "pkg:deb/ubuntu/nodejs@18.19.1+dfsg-6ubuntu5?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"18.13.0+dfsg1-1ubuntu2",
"18.19.1+dfsg-2ubuntu4",
"18.19.1+dfsg-6ubuntu1",
"18.19.1+dfsg-6ubuntu2",
"18.19.1+dfsg-6ubuntu5"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnode137",
"binary_version": "24.19.0+dfsg+~cs24.13.3-1ubuntu1"
},
{
"binary_name": "nodejs",
"binary_version": "24.19.0+dfsg+~cs24.13.3-1ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "nodejs",
"purl": "pkg:deb/ubuntu/nodejs@24.19.0+dfsg+~cs24.13.3-1ubuntu1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"22.22.1+dfsg+~cs22.19.15-1ubuntu1",
"24.16.0+dfsg+~cs24.13.1-2ubuntu1",
"24.18.0+dfsg+~cs24.13.2-1ubuntu1",
"24.19.0+dfsg+~cs24.13.3-1ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnode127",
"binary_version": "22.22.1+dfsg+~cs22.19.15-1ubuntu1"
},
{
"binary_name": "nodejs",
"binary_version": "22.22.1+dfsg+~cs22.19.15-1ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "nodejs",
"purl": "pkg:deb/ubuntu/nodejs@22.22.1+dfsg+~cs22.19.15-1ubuntu1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"20.19.4+dfsg-1",
"20.19.5+dfsg+~cs20.19.12-4",
"22.21.1+dfsg+~cs22.19.0-6ubuntu4",
"22.22.0+dfsg+~cs22.19.6-1ubuntu2",
"22.22.0+dfsg+~cs22.19.13-2ubuntu1",
"22.22.1+dfsg+~cs22.19.15-1ubuntu1"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2026-123871",
"modified": "2026-11-13T18:04:39Z",
"published": "2026-11-12T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-123871"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-123871"
},
{
"type": "REPORT",
"url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases#proxy-credentials-disclosed-in-err_proxy_invalid_config-error-messages-cve-2026-123871---medium"
},
{
"type": "REPORT",
"url": "https://cna.openjsf.org/security-advisories.html"
},
{
"type": "REPORT",
"url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-123871"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.