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.
CVE-2026-48615
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 38EG Risk 38/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15% - EPSS PROB
- 0.4%
- EPSS %ILE
- 32nd
- KEV
- Not listed
Published
June 26, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 26, 2026Node.js — Thursday, June 18, 2026 Security Releases
https://nodejs.org/en/blog/vulnerability/june-2026-security-releasesVendor Advisories for CVE-2026-48615(14)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:52399Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:22 security update
- RHSA-2026:41947Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:22 security, bug fix, and enhancement update
- RHSA-2026:39868Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:24 security, bug fix, and enhancement update
- RHSA-2026:39246Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs22 security update
- RHSA-2026:35892Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:22 security, bug fix, and enhancement update
- RHSA-2026:35891Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:24 security, bug fix, and enhancement update
- RHSA-2026:35842Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs22 security, bug fix, and enhancement update
- RHSA-2026:35841Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs24 security, bug fix, and enhancement update
- +6 more
Patch Availability(13)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | nodejs:22-9060020260804140259.rhel9 | 2026-08-10 | redhat |
| redhat | nodejs:22-8100020260703140402.6d880403 | 2026-07-20 | redhat |
| redhat | nodejs:24-8100020260630152626.6d880403 | 2026-07-15 | redhat |
| redhat | nodejs22-1:22.23.1-2.el10_0 | 2026-07-14 | redhat |
| redhat | nodejs:24-9080020260626074955.rhel9 | 2026-07-06 | redhat |
| redhat | nodejs24-1:24.18.0-1.el10_2 | 2026-07-06 | redhat |
| redhat | nodejs22-1:22.23.1-2.el10_2 | 2026-07-06 | redhat |
| redhat | nodejs:22-9080020260626075442.rhel9 | 2026-07-06 | redhat |
| redhat | nodejs26-main-26.4.0-1.2.hum1 | 2026-06-25 | redhat |
| redhat | nodejs24-main-24.18.0-0.1.hum1 | 2026-06-24 | redhat |
| redhat | nodejs22-main-22.23.1-1.hum1 | 2026-06-24 | redhat |
| redhat | nodejs20-main-20.20.2-1.hum1 | 2026-04-21 | redhat |
| redhat | nodejs25-main-25.9.0-1.1.hum1 | 2026-04-10 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| nodejs | 20.19.2+dfsg-1 ... 24.16.0+dfsg+~cs24.13.1-2 (38 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 33× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 291 total refreshes for this CVE.
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-26 00:27 UTCEPSS rescore
- 2026-09-23 17:53 UTCEPSS rescore
- 2026-09-23 08:22 UTCEG score recompute
- 2026-09-23 08:22 UTCVendor advisory
- 2026-09-23 08:22 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 07:17 UTCEG score recompute
- 2026-09-18 07:17 UTCVendor advisory
- 2026-09-18 07:17 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 01:15 UTCEG score recompute
- 2026-09-14 01:15 UTCVendor advisory
- 2026-09-14 01:15 UTCGHSA enrichment
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 09:35 UTCVendor advisory
- 2026-09-13 09:35 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-12 15:40 UTCEG score recompute
- 2026-09-12 15:40 UTCVendor advisory
- 2026-09-12 15:40 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:27 UTCEG score recompute
- 2026-08-30 19:27 UTCVendor advisory
- 2026-08-30 19:26 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 23:15 UTCEG score recompute
- 2026-08-27 23:15 UTCVendor advisory
- 2026-08-27 23:15 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 01:05 UTCEG score recompute
- 2026-08-25 01:05 UTCVendor advisory
- 2026-08-25 01:05 UTCGHSA enrichment
- 2026-08-24 13:07 UTCEG score recompute
- 2026-08-24 13:07 UTCVendor advisory
- 2026-08-24 13:07 UTCGHSA enrichment
- 2026-08-23 22:24 UTCVendor advisory
- 2026-08-23 22:24 UTCGHSA enrichment
- 2026-08-23 10:27 UTCEG score recompute
- 2026-08-23 10:27 UTCVendor advisory
- 2026-08-23 10:27 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 22:18 UTCVendor advisory
- 2026-08-22 22:18 UTCGHSA enrichment
- 2026-08-22 09:52 UTCEG score recompute
- 2026-08-22 09:52 UTCVendor advisory
- 2026-08-22 09:52 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 19:11 UTCVendor advisory
- 2026-08-21 19:11 UTCGHSA enrichment
- 2026-08-21 07:14 UTCEG score recompute
- 2026-08-21 07:14 UTCVendor advisory
- 2026-08-21 07:14 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 18:56 UTCVendor advisory
- 2026-08-20 18:56 UTCGHSA enrichment
- 2026-08-20 06:59 UTCEG score recompute
- 2026-08-20 06:59 UTCVendor advisory
- 2026-08-20 06:59 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 13:08 UTCVendor advisory
- 2026-08-19 13:08 UTCGHSA enrichment
- 2026-08-19 01:11 UTCEG score recompute
- 2026-08-19 01:11 UTCVendor advisory
- 2026-08-19 01:11 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 08:13 UTCVendor advisory
- 2026-08-17 08:13 UTCGHSA enrichment
- 2026-08-16 20:17 UTCEG score recompute
- 2026-08-16 20:17 UTCVendor advisory
- 2026-08-16 20:17 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:20 UTCEG score recompute
- 2026-08-16 08:20 UTCVendor advisory
- 2026-08-16 08:20 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 20:23 UTCVendor advisory
- 2026-08-15 20:23 UTCGHSA enrichment
- 2026-08-15 08:25 UTCEG score recompute
- 2026-08-15 08:25 UTCVendor advisory
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownAlpine:v3.21:nodejs
- CVE-2026-48930EG 9.8CRITICAL
- CVE-2023-32559NVD 7.5EG 9.8CRITICAL
- CVE-2023-32002EG 9.8CRITICAL
- CVE-2022-35256NVD 6.5EG 9.8CRITICAL
- CVE-2021-22930EG 9.8EPSS p98CRITICAL
- CVE-2019-15606EG 9.8EPSS p97CRITICAL
- CVE-2019-15605EG 9.8EPSS p99CRITICAL
- CVE-2025-55130EG 9.1CRITICAL
- CVE-2022-35255EG 9.1CRITICAL
- CVE-2022-32215NVD 6.5EG 9.1EPSS p99CRITICAL
Same vendor
10 shownredhat:RHSA-2026:28727 · redhat:RHSA-2026:35841
Frequently asked(5)
What is CVE-2026-48615?
When was CVE-2026-48615 disclosed?
Is CVE-2026-48615 actively exploited?
What is the CVSS score of CVE-2026-48615?
How do I remediate CVE-2026-48615?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48615
Is Your Infrastructure Affected by CVE-2026-48615?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.