CVE-2026-48615

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
No patch confirmed yet.
generic

Node.js — Thursday, June 18, 2026 Security Releases

https://nodejs.org/en/blog/vulnerability/june-2026-security-releases

Vendor 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.

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs:22-9060020260804140259.rhel92026-08-10redhat
redhatnodejs:22-8100020260703140402.6d8804032026-07-20redhat
redhatnodejs:24-8100020260630152626.6d8804032026-07-15redhat
redhatnodejs22-1:22.23.1-2.el10_02026-07-14redhat
redhatnodejs:24-9080020260626074955.rhel92026-07-06redhat
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatnodejs22-1:22.23.1-2.el10_22026-07-06redhat
redhatnodejs:22-9080020260626075442.rhel92026-07-06redhat
redhatnodejs26-main-26.4.0-1.2.hum12026-06-25redhat
redhatnodejs24-main-24.18.0-0.1.hum12026-06-24redhat
redhatnodejs22-main-22.23.1-1.hum12026-06-24redhat
redhatnodejs20-main-20.20.2-1.hum12026-04-21redhat
redhatnodejs25-main-25.9.0-1.1.hum12026-04-10redhat

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)
PackageVulnerable rangeFixed inDependents
nodejs—22.23.0-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
nodejs—22.23.0-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.17.0-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.17.0-r0—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.16.0+dfsg+~cs24.13.1-2 (38 versions)24.17.0+dfsg+~cs24.13.2-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 35× in last 7d / 148× 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 222 total refreshes for this CVE.

  1. 2026-08-21 07:14 UTCEG score recompute
  2. 2026-08-21 07:14 UTCVendor advisory
  3. 2026-08-21 07:14 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 18:56 UTCVendor advisory
  6. 2026-08-20 18:56 UTCGHSA enrichment
  7. 2026-08-20 06:59 UTCEG score recompute
  8. 2026-08-20 06:59 UTCVendor advisory
  9. 2026-08-20 06:59 UTCGHSA enrichment
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-19 13:08 UTCVendor advisory
  12. 2026-08-19 13:08 UTCGHSA enrichment
  13. 2026-08-19 01:11 UTCEG score recompute
  14. 2026-08-19 01:11 UTCVendor advisory
  15. 2026-08-19 01:11 UTCGHSA enrichment
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 08:13 UTCVendor advisory
  19. 2026-08-17 08:13 UTCGHSA enrichment
  20. 2026-08-16 20:17 UTCEG score recompute
  21. 2026-08-16 20:17 UTCVendor advisory
  22. 2026-08-16 20:17 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 08:20 UTCEG score recompute
  25. 2026-08-16 08:20 UTCVendor advisory
Show 75 more
  1. 2026-08-16 08:20 UTCGHSA enrichment
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 20:23 UTCVendor advisory
  4. 2026-08-15 20:23 UTCGHSA enrichment
  5. 2026-08-15 08:25 UTCEG score recompute
  6. 2026-08-15 08:25 UTCVendor advisory
  7. 2026-08-15 08:25 UTCGHSA enrichment
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 18:19 UTCVendor advisory
  10. 2026-08-14 18:19 UTCGHSA enrichment
  11. 2026-08-14 06:23 UTCEG score recompute
  12. 2026-08-14 06:23 UTCVendor advisory
  13. 2026-08-14 06:23 UTCGHSA enrichment
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 18:26 UTCVendor advisory
  16. 2026-08-13 18:26 UTCGHSA enrichment
  17. 2026-08-13 05:07 UTCVendor advisory
  18. 2026-08-13 05:07 UTCGHSA enrichment
  19. 2026-08-12 17:09 UTCEG score recompute
  20. 2026-08-12 17:09 UTCVendor advisory
  21. 2026-08-12 17:09 UTCGHSA enrichment
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-12 05:06 UTCVendor advisory
  24. 2026-08-12 05:06 UTCGHSA enrichment
  25. 2026-08-11 17:09 UTCEG score recompute
  26. 2026-08-11 17:09 UTCVendor advisory
  27. 2026-08-11 17:09 UTCGHSA enrichment
  28. 2026-08-11 05:10 UTCEG score recompute
  29. 2026-08-11 05:10 UTCVendor advisory
  30. 2026-08-11 05:10 UTCGHSA enrichment
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-10 17:14 UTCVendor advisory
  33. 2026-08-10 17:14 UTCGHSA enrichment
  34. 2026-08-10 04:30 UTCVendor advisory
  35. 2026-08-10 04:30 UTCGHSA enrichment
  36. 2026-08-09 16:32 UTCEG score recompute
  37. 2026-08-09 16:32 UTCVendor advisory
  38. 2026-08-09 16:32 UTCGHSA enrichment
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-09 04:36 UTCVendor advisory
  41. 2026-08-09 04:36 UTCGHSA enrichment
  42. 2026-08-08 16:39 UTCEG score recompute
  43. 2026-08-08 16:39 UTCVendor advisory
  44. 2026-08-08 16:39 UTCGHSA enrichment
  45. 2026-08-08 16:37 UTCEPSS rescore
  46. 2026-08-08 04:42 UTCVendor advisory
  47. 2026-08-08 04:42 UTCGHSA enrichment
  48. 2026-08-07 16:46 UTCEG score recompute
  49. 2026-08-07 16:46 UTCVendor advisory
  50. 2026-08-07 16:46 UTCGHSA enrichment
  51. 2026-08-07 04:49 UTCVendor advisory
  52. 2026-08-07 04:49 UTCGHSA enrichment
  53. 2026-08-06 16:52 UTCEG score recompute
  54. 2026-08-06 16:52 UTCVendor advisory
  55. 2026-08-06 16:52 UTCGHSA enrichment
  56. 2026-08-06 13:47 UTCEPSS rescore
  57. 2026-08-06 04:55 UTCEG score recompute
  58. 2026-08-06 04:55 UTCVendor advisory
  59. 2026-08-06 04:55 UTCGHSA enrichment
  60. 2026-08-05 19:17 UTCEPSS rescore
  61. 2026-08-05 16:58 UTCVendor advisory
  62. 2026-08-05 16:58 UTCGHSA enrichment
  63. 2026-08-05 02:59 UTCEG score recompute
  64. 2026-08-05 02:59 UTCVendor advisory
  65. 2026-08-05 02:59 UTCGHSA enrichment
  66. 2026-08-04 15:10 UTCEPSS rescore
  67. 2026-08-04 15:02 UTCEG score recompute
  68. 2026-08-04 15:02 UTCVendor advisory
  69. 2026-08-04 15:02 UTCGHSA enrichment
  70. 2026-08-04 10:39 UTCEPSS rescore
  71. 2026-08-04 02:51 UTCVendor advisory
  72. 2026-08-04 02:51 UTCGHSA enrichment
  73. 2026-08-03 14:45 UTCVendor advisory
  74. 2026-08-03 14:45 UTCGHSA enrichment
  75. 2026-08-03 02:48 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-48615?
CVE-2026-48615 is a high vulnerability published on June 26, 2026. A flaw in Node.js proxy tunnel error handling could expose proxy credentials in ERRPROXYTUNNEL 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…
When was CVE-2026-48615 disclosed?
CVE-2026-48615 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48615 actively exploited?
CVE-2026-48615 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.6% of all scored CVEs.
What is the CVSS score of CVE-2026-48615?
CVE-2026-48615 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-48615?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48615, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48615

Explore →

Is Your Infrastructure Affected by CVE-2026-48615?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs