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.

Affected Packages

(8 across 8 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:11(1)
PackageVulnerable rangeFixed inDependents
nodejs12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nodejs18.13.0+dfsg1-1 ... 24.20.0+dfsg+~cs24.13.3-2 (90 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.20.0+dfsg+~cs24.13.3-2 (45 versions)——
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 13× in last 7d / 48× 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 202 total refreshes for this CVE.

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

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

See which npm, PyPI, Go, and Maven packages are affected by 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