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 — 4 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 2%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
82.9%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 21, 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(13)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-17 00:52 UTCVendor advisory
  9. 2026-07-17 00:52 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 12:29 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  12. 2026-07-16 11:42 UTCVendor advisory
  13. 2026-07-16 11:42 UTCGHSA enrichment
  14. 2026-07-15 22:32 UTCVendor advisory
  15. 2026-07-15 22:32 UTCGHSA enrichment
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 09:22 UTCVendor advisory
  18. 2026-07-15 09:22 UTCGHSA enrichment
  19. 2026-07-15 03:14 UTCMITRE cvelistV5CVSS v3 → 7.7 · severity → HIGH
  20. 2026-07-15 02:26 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  21. 2026-07-15 02:06 UTCMITRE cvelistV5CVSS v3 → 7.7 · severity → HIGH
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-14 20:09 UTCVendor advisory
  24. 2026-07-14 20:09 UTCGHSA enrichment
  25. 2026-07-14 07:00 UTCVendor advisory
Show 75 more
  1. 2026-07-14 07:00 UTCGHSA enrichment
  2. 2026-07-13 22:30 UTCEPSS rescore
  3. 2026-07-13 17:49 UTCVendor advisory
  4. 2026-07-13 17:49 UTCGHSA enrichment
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-13 04:39 UTCVendor advisory
  7. 2026-07-13 04:39 UTCGHSA enrichment
  8. 2026-07-12 15:28 UTCVendor advisory
  9. 2026-07-12 15:27 UTCGHSA enrichment
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-12 02:16 UTCVendor advisory
  12. 2026-07-12 02:16 UTCGHSA enrichment
  13. 2026-07-11 13:06 UTCVendor advisory
  14. 2026-07-11 13:06 UTCGHSA enrichment
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-10 23:55 UTCVendor advisory
  17. 2026-07-10 23:55 UTCGHSA enrichment
  18. 2026-07-10 10:45 UTCVendor advisory
  19. 2026-07-10 10:45 UTCGHSA enrichment
  20. 2026-07-09 21:24 UTCVendor advisory
  21. 2026-07-09 21:24 UTCGHSA enrichment
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-09 08:15 UTCVendor advisory
  24. 2026-07-09 08:15 UTCGHSA enrichment
  25. 2026-07-08 19:05 UTCVendor advisory
  26. 2026-07-08 19:05 UTCGHSA enrichment
  27. 2026-07-08 15:16 UTCEPSS rescore
  28. 2026-07-08 05:55 UTCVendor advisory
  29. 2026-07-08 05:55 UTCGHSA enrichment
  30. 2026-07-07 16:39 UTCVendor advisory
  31. 2026-07-07 16:39 UTCGHSA enrichment
  32. 2026-07-07 13:46 UTCEPSS rescore
  33. 2026-07-07 03:14 UTCVendor advisory
  34. 2026-07-07 03:14 UTCGHSA enrichment
  35. 2026-07-06 16:27 UTCEPSS rescore
  36. 2026-07-06 14:05 UTCVendor advisory
  37. 2026-07-06 14:05 UTCGHSA enrichment
  38. 2026-07-06 02:23 UTCEPSS rescore
  39. 2026-07-06 00:51 UTCVendor advisory
  40. 2026-07-06 00:51 UTCGHSA enrichment
  41. 2026-07-05 11:41 UTCVendor advisory
  42. 2026-07-05 11:41 UTCGHSA enrichment
  43. 2026-07-05 02:30 UTCEPSS rescore
  44. 2026-07-04 22:31 UTCVendor advisory
  45. 2026-07-04 22:31 UTCGHSA enrichment
  46. 2026-07-04 09:20 UTCVendor advisory
  47. 2026-07-04 09:20 UTCGHSA enrichment
  48. 2026-07-04 06:31 UTCEPSS rescore
  49. 2026-07-03 20:11 UTCVendor advisory
  50. 2026-07-03 20:11 UTCGHSA enrichment
  51. 2026-07-03 07:00 UTCVendor advisory
  52. 2026-07-03 07:00 UTCGHSA enrichment
  53. 2026-07-02 17:47 UTCVendor advisory
  54. 2026-07-02 17:46 UTCGHSA enrichment
  55. 2026-07-02 04:37 UTCVendor advisory
  56. 2026-07-02 04:37 UTCGHSA enrichment
  57. 2026-07-01 15:27 UTCVendor advisory
  58. 2026-07-01 15:26 UTCGHSA enrichment
  59. 2026-07-01 15:07 UTCEPSS rescore
  60. 2026-07-01 02:17 UTCVendor advisory
  61. 2026-07-01 02:17 UTCGHSA enrichment
  62. 2026-06-30 23:22 UTCEPSS rescore
  63. 2026-06-30 13:07 UTCVendor advisory
  64. 2026-06-30 13:07 UTCGHSA enrichment
  65. 2026-06-29 23:56 UTCVendor advisory
  66. 2026-06-29 23:55 UTCGHSA enrichment
  67. 2026-06-29 14:06 UTCEPSS rescore
  68. 2026-06-29 14:06 UTCEPSS rescore
  69. 2026-06-29 10:46 UTCVendor advisory
  70. 2026-06-29 10:46 UTCGHSA enrichment
  71. 2026-06-28 21:36 UTCVendor advisory
  72. 2026-06-28 21:36 UTCGHSA enrichment
  73. 2026-06-28 14:07 UTCEPSS rescore
  74. 2026-06-28 08:26 UTCVendor advisory
  75. 2026-06-28 08:26 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, with the most recent update on July 21, 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 82.9% 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