CVE-2026-48928

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% 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
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

A fix is available — apply it.

A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity54% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
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-48928(12)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs:22-8100020260703140402.6d8804032026-07-20redhat
redhatnodejs:24-8100020260630152626.6d8804032026-07-15redhat
redhatnodejs22-1:22.23.1-2.el10_22026-07-06redhat
redhatnodejs:24-9080020260626074955.rhel92026-07-06redhat
redhatnodejs:22-9080020260626075442.rhel92026-07-06redhat
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatnodejs22-main-22.23.1-2.hum12026-07-03redhat
redhatnodejs24-main-24.18.0-0.2.hum12026-07-01redhat
redhatnodejs26-main-26.4.0-1.3.hum12026-06-30redhat
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 66× 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.

  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:43 UTCEG score recompute
  3. 2026-07-26 14:43 UTCVendor advisory
  4. 2026-07-26 14:43 UTCGHSA enrichment
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-24 14:18 UTCEPSS rescore
  7. 2026-07-23 14:18 UTCEPSS rescore
  8. 2026-07-23 03:18 UTCEG score recompute▲ 1.20
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-21 15:25 UTCEPSS rescore
  11. 2026-07-20 17:08 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-19 02:29 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-16 21:14 UTCVendor advisory
  17. 2026-07-16 21:14 UTCGHSA enrichment
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-15 20:22 UTCVendor advisory
  20. 2026-07-15 20:22 UTCGHSA enrichment
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-14 19:30 UTCVendor advisory
  24. 2026-07-14 19:30 UTCGHSA enrichment
  25. 2026-07-13 22:30 UTCEPSS rescore
Show 46 more
  1. 2026-07-13 18:38 UTCVendor advisory
  2. 2026-07-13 18:38 UTCGHSA enrichment
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-12 17:46 UTCVendor advisory
  5. 2026-07-12 17:46 UTCGHSA enrichment
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 16:52 UTCVendor advisory
  8. 2026-07-11 16:52 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-10 16:00 UTCVendor advisory
  11. 2026-07-10 16:00 UTCGHSA enrichment
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-09 15:07 UTCVendor advisory
  14. 2026-07-09 15:07 UTCGHSA enrichment
  15. 2026-07-08 15:16 UTCEPSS rescore
  16. 2026-07-08 14:14 UTCVendor advisory
  17. 2026-07-08 14:14 UTCGHSA enrichment
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-07 13:23 UTCVendor advisory
  20. 2026-07-07 13:23 UTCGHSA enrichment
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 12:31 UTCVendor advisory
  23. 2026-07-06 12:31 UTCGHSA enrichment
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-05 11:39 UTCGHSA enrichment
  26. 2026-07-05 02:30 UTCEPSS rescore
  27. 2026-07-04 10:45 UTCGHSA enrichment
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-03 09:50 UTCGHSA enrichment
  30. 2026-07-02 08:58 UTCGHSA enrichment
  31. 2026-07-01 15:07 UTCEPSS rescore
  32. 2026-07-01 08:07 UTCGHSA enrichment
  33. 2026-06-30 23:22 UTCEPSS rescore
  34. 2026-06-30 07:15 UTCGHSA enrichment
  35. 2026-06-29 14:06 UTCEPSS rescore
  36. 2026-06-29 14:06 UTCEPSS rescore
  37. 2026-06-29 06:23 UTCGHSA enrichment
  38. 2026-06-28 14:07 UTCEPSS rescore
  39. 2026-06-28 05:30 UTCGHSA enrichment
  40. 2026-06-28 04:56 UTCEPSS rescore
  41. 2026-06-28 04:56 UTCEPSS rescore
  42. 2026-06-27 04:38 UTCGHSA enrichment
  43. 2026-06-27 03:08 UTCEPSS rescore
  44. 2026-06-26 21:42 UTCNVD updateCVSS v3 → 5.4
  45. 2026-06-26 03:46 UTCEG score recompute
  46. 2026-06-26 03:46 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48928?
CVE-2026-48928 is a medium vulnerability published on June 26, 2026. A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.
When was CVE-2026-48928 disclosed?
CVE-2026-48928 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-48928 actively exploited?
CVE-2026-48928 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 87.9% of all scored CVEs.
What is the CVSS score of CVE-2026-48928?
CVE-2026-48928 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-48928?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48928, 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

Explore the affected products and dependency analysis for CVE-2026-48928

Explore →

Is Your Infrastructure Affected by CVE-2026-48928?

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

Start Free Scan →Browse All CVEs