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
Trending — 4 sources updated this week
7.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 6.5Exploit: None knownExposed: 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)
EG Risk
36(Track)
EG Risk 36/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
Severity77% × 45%
Exploitation3% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
87%
KEV
Not listed

Published

June 26, 2026

Last Modified

August 10, 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

Patch Availability(13)

Vendor / EcosystemFixed in / 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 rangeFixed inDependents
nodejs22.23.0-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
nodejs22.23.0-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
nodejs24.17.0-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
nodejs24.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.18.0+dfsg+~cs24.13.2-1 (87 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (42 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(2)

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

Data Freshness Timeline

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

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

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 12.8% of all 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.
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

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.