Skip to main content
VulnerabilityPublished

CVE-2026-48615: nodejs node · Privacy Violation

Affects nodejs nodeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.0 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • >=22.22.3 <=22.22.3
  • >=24.16.0 <=24.16.0
  • >=26.3.0 <=26.3.0
Fixed in–

AI-suggested

Until an official fix is available, avoid embedding proxy credentials directly in proxy URLs or ensure that error messages and logs do not capture sensitive information. Monitor vendor communications for updates on patches or official mitigations.

Description

A flaw in Node.js proxy tunnel error handling could expose proxy credentials in `ERR_PROXY_TUNNEL` error messages. When proxy credentials are embedded in the proxy URL, they may be exposed through error handling paths and captured by logs, diagnostics, or other error consumers. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

References

Community reviews

Loading reviews…