CVE-2026-48618

MEDIUMNVD 6.57.7▲
EchelonGraph scoreMEDIUM confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. NVD baseline CVSS 6.5; sources differ by 1.2.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — Patch released this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.5Exploit: NoneExposed: 0

A fix is available — apply it.

A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.

CVSS v3
6.5
EG Score
7.7(medium)
EPSS
47.7%
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-48618(7)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs:22-9080020260626075442.rhel92026-07-06redhat
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatnodejs22-1:22.23.1-2.el10_22026-07-06redhat
redhatnodejs:24-9080020260626074955.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.

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 45× in last 7d / 74× 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-07 03:14 UTCEG score recompute
  2. 2026-07-07 03:14 UTCVendor advisory
  3. 2026-07-07 03:14 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 14:05 UTCEG score recompute
  6. 2026-07-06 14:05 UTCVendor advisory
  7. 2026-07-06 14:05 UTCGHSA enrichment
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 00:51 UTCEG score recompute
  10. 2026-07-06 00:51 UTCVendor advisory
  11. 2026-07-06 00:51 UTCGHSA enrichment
  12. 2026-07-05 11:41 UTCEG score recompute
  13. 2026-07-05 11:41 UTCVendor advisory
  14. 2026-07-05 11:41 UTCGHSA enrichment
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-04 22:31 UTCEG score recompute
  17. 2026-07-04 22:31 UTCVendor advisory
  18. 2026-07-04 22:31 UTCGHSA enrichment
  19. 2026-07-04 09:20 UTCEG score recompute
  20. 2026-07-04 09:20 UTCVendor advisory
  21. 2026-07-04 09:20 UTCGHSA enrichment
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-03 20:11 UTCEG score recompute
  24. 2026-07-03 20:11 UTCVendor advisory
  25. 2026-07-03 20:11 UTCGHSA enrichment
Show 49 more
  1. 2026-07-03 07:00 UTCEG score recompute
  2. 2026-07-03 07:00 UTCVendor advisory
  3. 2026-07-03 07:00 UTCGHSA enrichment
  4. 2026-07-02 17:47 UTCEG score recompute
  5. 2026-07-02 17:47 UTCVendor advisory
  6. 2026-07-02 17:46 UTCGHSA enrichment
  7. 2026-07-02 04:37 UTCEG score recompute
  8. 2026-07-02 04:37 UTCVendor advisory
  9. 2026-07-02 04:37 UTCGHSA enrichment
  10. 2026-07-01 15:27 UTCEG score recompute
  11. 2026-07-01 15:27 UTCVendor advisory
  12. 2026-07-01 15:26 UTCGHSA enrichment
  13. 2026-07-01 15:07 UTCEPSS rescore
  14. 2026-07-01 02:17 UTCEG score recompute
  15. 2026-07-01 02:17 UTCVendor advisory
  16. 2026-07-01 02:17 UTCGHSA enrichment
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-30 13:07 UTCEG score recompute
  19. 2026-06-30 13:07 UTCVendor advisory
  20. 2026-06-30 13:07 UTCGHSA enrichment
  21. 2026-06-29 23:56 UTCEG score recompute
  22. 2026-06-29 23:56 UTCVendor advisory
  23. 2026-06-29 23:55 UTCGHSA enrichment
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
  26. 2026-06-29 10:46 UTCEG score recompute
  27. 2026-06-29 10:46 UTCVendor advisory
  28. 2026-06-29 10:46 UTCGHSA enrichment
  29. 2026-06-28 21:36 UTCEG score recompute
  30. 2026-06-28 21:36 UTCVendor advisory
  31. 2026-06-28 21:36 UTCGHSA enrichment
  32. 2026-06-28 14:07 UTCEPSS rescore
  33. 2026-06-28 08:26 UTCEG score recompute
  34. 2026-06-28 08:26 UTCVendor advisory
  35. 2026-06-28 08:26 UTCGHSA enrichment
  36. 2026-06-28 04:56 UTCEPSS rescore
  37. 2026-06-28 04:56 UTCEPSS rescore
  38. 2026-06-27 19:16 UTCEG score recompute
  39. 2026-06-27 19:16 UTCVendor advisory
  40. 2026-06-27 19:16 UTCGHSA enrichment
  41. 2026-06-27 06:06 UTCEG score recompute
  42. 2026-06-27 06:06 UTCVendor advisory
  43. 2026-06-27 06:06 UTCGHSA enrichment
  44. 2026-06-27 03:08 UTCEPSS rescore
  45. 2026-06-26 21:42 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  46. 2026-06-26 16:56 UTCEG score recompute
  47. 2026-06-26 16:56 UTCGHSA enrichment
  48. 2026-06-26 03:46 UTCEG score recompute
  49. 2026-06-26 03:46 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-48618?
CVE-2026-48618 is a medium vulnerability published on June 26, 2026. A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat. This can lead to confidentiality impact or bypass of the intended security boundary under…
When was CVE-2026-48618 disclosed?
CVE-2026-48618 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-48618 actively exploited?
CVE-2026-48618 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 47.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48618?
CVE-2026-48618 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.7.
How do I remediate CVE-2026-48618?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48618, 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-48618

Explore →

Is Your Infrastructure Affected by CVE-2026-48618?

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

Start Free Scan →Browse All CVEs