CVE-2026-48618

HIGHNVD 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
7.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 3.2%CVSS: 6.5Exploit: None knownExposed services: Not assessed

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.7HIGHmedium confidence
EG Risk
36
EG Risk 36/100

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
Severity77% × 45%
Exploitation3% × 40%
Automatability0% × 15%
EPSS PROB
3.2%
EPSS %ILE
87th
KEV
Not listed

Published

June 26, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
Patch available.
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(14)

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs:22-9060020260804140259.rhel92026-08-10redhat
redhatnodejs:22-8100020260703140402.6d8804032026-07-20redhat
redhatnodejs:24-8100020260630152626.6d8804032026-07-15redhat
redhatnodejs22-1:22.23.1-2.el10_02026-07-14redhat
redhatnodejs:24-9080020260626074955.rhel92026-07-06redhat
redhatnodejs:22-9080020260626075442.rhel92026-07-06redhat
redhatnodejs22-1:22.23.1-2.el10_22026-07-06redhat
redhatnodejs24-1:24.18.0-1.el10_22026-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.

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.0-r0: fixed in 22.23.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.0-r0: fixed in 22.23.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.17.0-r0: fixed in 24.17.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.17.0-r0: fixed in 24.17.0-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs18.13.0+dfsg1-1 ... 18.20.4+dfsg-1~deb12u2 (22 versions)
  • every version up to 18.20.4+dfsg-1~deb12u3: fixed in 18.20.4+dfsg-1~deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2
  • every version up to 20.19.2+dfsg-1+deb13u3: fixed in 20.19.2+dfsg-1+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1 ... 24.16.0+dfsg+~cs24.13.1-2 (38 versions)
  • every version up to 24.17.0+dfsg+~cs24.13.2-1: fixed in 24.17.0+dfsg+~cs24.13.2-1
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48618?
CVE-2026-48618 is a high 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 on June 26, 2026, with the most recent update on August 10, 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 3.2% probability of exploitation in the next 30 days (87th percentile of EPSS-scored CVEs).
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 (HIGH).
How do I remediate CVE-2026-48618?
A fix for CVE-2026-48618 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48618 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Book a Demo →Browse All CVEs