CVE-2026-48928

MEDIUMNVD 5.44.2▼
EchelonGraph scoreMEDIUM confidence

Score 4.2 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.4; sources differ by 1.2.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — Patch released this week
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: NoneExposed: 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
4.2(medium)
EPSS
16.9%
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(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatnodejs22-1:22.23.1-2.el10_22026-07-06redhat

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.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 21× in last 7d / 36× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 12:31 UTCEG score recompute
  3. 2026-07-06 12:31 UTCVendor advisory
  4. 2026-07-06 12:31 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 11:39 UTCEG score recompute
  7. 2026-07-05 11:39 UTCGHSA enrichment
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 10:45 UTCEG score recompute
  10. 2026-07-04 10:45 UTCGHSA enrichment
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 09:50 UTCEG score recompute
  13. 2026-07-03 09:50 UTCGHSA enrichment
  14. 2026-07-02 08:58 UTCEG score recompute
  15. 2026-07-02 08:58 UTCGHSA enrichment
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-07-01 08:07 UTCEG score recompute
  18. 2026-07-01 08:07 UTCGHSA enrichment
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 07:15 UTCEG score recompute
  21. 2026-06-30 07:15 UTCGHSA enrichment
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 06:23 UTCEG score recompute
  25. 2026-06-29 06:23 UTCGHSA enrichment
Show 11 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 05:30 UTCEG score recompute
  3. 2026-06-28 05:30 UTCGHSA enrichment
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 04:39 UTCEG score recompute
  7. 2026-06-27 04:38 UTCGHSA enrichment
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-26 21:42 UTCNVD updateCVSS v3 → 5.4
  10. 2026-06-26 03:46 UTCEG score recompute
  11. 2026-06-26 03:46 UTCGHSA enrichment

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 16.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48928?
CVE-2026-48928 has a CVSS v3 base score of 5.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 4.2.
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