Quick answers
- Is CVE-2026-123871 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123871 being exploited in the wild.
- How severe is CVE-2026-123871?
- Medium severity, with a CVSS score of 6.2, published 11 November 2026.
- Which products and versions are affected?
- OpenJS Foundation Node.js 26.x, 24.x, 22.x.
- Is there a fix for CVE-2026-123871?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-123871 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-123871?
- Check whether you run OpenJS Foundation Node.js at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an information disclosure flaw in Node.js proxy configuration error handling. Four error paths in the proxy subsystem interpolate the raw proxy URL (including credentials) from environment variables into ERR_PROXY_INVALID_CONFIG error messages, bypassing redaction logic that was added in CVE-2026-48615. The attack vector is the application's logging and monitoring infrastructure; an attacker with read access to stderr, container logs, or log aggregation and crash reporting systems can extract proxy credentials.
Affected products
- OpenJS Foundation Node.js 26.x, 24.x, 22.x
Timeline
- 2026-11-11: disclosed