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.
CVE-2026-48618
Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. NVD baseline CVSS 6.5; sources differ by 1.2.
- Lower severity and no public exploit yet
A fix is available — apply it.
- 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 computedSeverity77% × 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, 2026Node.js — Thursday, June 18, 2026 Security Releases
https://nodejs.org/en/blog/vulnerability/june-2026-security-releasesVendor 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.
- RHSA-2026:52399Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:22 security update
- RHSA-2026:41947Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:22 security, bug fix, and enhancement update
- RHSA-2026:39868Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:24 security, bug fix, and enhancement update
- RHSA-2026:39246Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs22 security update
- RHSA-2026:35892Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:22 security, bug fix, and enhancement update
- RHSA-2026:35891Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:24 security, bug fix, and enhancement update
- RHSA-2026:35842Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs22 security, bug fix, and enhancement update
- RHSA-2026:35841Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs24 security, bug fix, and enhancement update
- +6 more
Patch Availability(13)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | nodejs:22-9060020260804140259.rhel9 | 2026-08-10 | redhat |
| redhat | nodejs:22-8100020260703140402.6d880403 | 2026-07-20 | redhat |
| redhat | nodejs:24-8100020260630152626.6d880403 | 2026-07-15 | redhat |
| redhat | nodejs22-1:22.23.1-2.el10_0 | 2026-07-14 | redhat |
| redhat | nodejs:24-9080020260626074955.rhel9 | 2026-07-06 | redhat |
| redhat | nodejs:22-9080020260626075442.rhel9 | 2026-07-06 | redhat |
| redhat | nodejs22-1:22.23.1-2.el10_2 | 2026-07-06 | redhat |
| redhat | nodejs24-1:24.18.0-1.el10_2 | 2026-07-06 | redhat |
| redhat | nodejs26-main-26.4.0-1.2.hum1 | 2026-06-25 | redhat |
| redhat | nodejs24-main-24.18.0-0.1.hum1 | 2026-06-24 | redhat |
| redhat | nodejs22-main-22.23.1-1.hum1 | 2026-06-24 | redhat |
| redhat | nodejs20-main-20.20.2-1.hum1 | 2026-04-21 | redhat |
| redhat | nodejs25-main-25.9.0-1.1.hum1 | 2026-04-10 | redhat |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | — | 22.23.0-r0 | — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | — | 22.23.0-r0 | — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | — | 24.17.0-r0 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | — | 24.17.0-r0 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | 12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | 18.13.0+dfsg1-1 ... 24.18.0+dfsg+~cs24.13.2-1 (87 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | 20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (42 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodejs | 20.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.
- 2026-08-20 06:59 UTCEG score recompute
- 2026-08-20 06:59 UTCVendor advisory
- 2026-08-20 06:59 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 14:42 UTCVendor advisory
- 2026-08-19 14:41 UTCGHSA enrichment
- 2026-08-19 01:11 UTCEG score recompute
- 2026-08-19 01:11 UTCVendor advisory
- 2026-08-19 01:11 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 17:05 UTCEG score recompute
- 2026-08-17 17:05 UTCVendor advisory
- 2026-08-17 17:05 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 03:54 UTCEG score recompute
- 2026-08-17 03:54 UTCVendor advisory
- 2026-08-17 03:54 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:44 UTCEG score recompute
- 2026-08-16 14:44 UTCVendor advisory
- 2026-08-16 14:44 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 01:34 UTCVendor advisory
- 2026-08-16 01:34 UTCGHSA enrichment
- 2026-08-15 12:24 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-15 12:24 UTCVendor advisory
- 2026-08-15 12:24 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 23:14 UTCVendor advisory
- 2026-08-14 23:14 UTCGHSA enrichment
- 2026-08-14 10:05 UTCEG score recompute
- 2026-08-14 10:05 UTCVendor advisory
- 2026-08-14 10:05 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 20:55 UTCVendor advisory
- 2026-08-13 20:55 UTCGHSA enrichment
- 2026-08-13 07:45 UTCVendor advisory
- 2026-08-13 07:45 UTCGHSA enrichment
- 2026-08-12 17:59 UTCEG score recompute
- 2026-08-12 17:59 UTCVendor advisory
- 2026-08-12 17:59 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 04:49 UTCVendor advisory
- 2026-08-12 04:49 UTCGHSA enrichment
- 2026-08-11 15:39 UTCEG score recompute
- 2026-08-11 15:39 UTCVendor advisory
- 2026-08-11 15:39 UTCGHSA enrichment
- 2026-08-11 02:30 UTCEG score recompute
- 2026-08-11 02:30 UTCVendor advisory
- 2026-08-11 02:30 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 13:20 UTCVendor advisory
- 2026-08-10 13:20 UTCGHSA enrichment
- 2026-08-10 12:25 UTCVendor advisory
- 2026-08-10 12:25 UTCGHSA enrichment
- 2026-08-10 06:47 UTCVendor advisory
- 2026-08-10 06:47 UTCGHSA enrichment
- 2026-08-09 17:38 UTCVendor advisory
- 2026-08-09 17:38 UTCGHSA enrichment
- 2026-08-09 04:28 UTCEG score recompute
- 2026-08-09 04:28 UTCVendor advisory
- 2026-08-09 04:28 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 15:19 UTCVendor advisory
- 2026-08-08 15:19 UTCGHSA enrichment
- 2026-08-08 02:08 UTCEG score recompute
- 2026-08-08 02:08 UTCVendor advisory
- 2026-08-08 02:08 UTCGHSA enrichment
- 2026-08-07 12:58 UTCVendor advisory
- 2026-08-07 12:58 UTCGHSA enrichment
- 2026-08-06 23:48 UTCEG score recompute
- 2026-08-06 23:48 UTCVendor advisory
- 2026-08-06 23:48 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 10:39 UTCVendor advisory
- 2026-08-06 10:39 UTCGHSA enrichment
- 2026-08-05 21:29 UTCEG score recompute
- 2026-08-05 21:29 UTCVendor advisory
- 2026-08-05 21:29 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 08:20 UTCEG score recompute
- 2026-08-05 08:20 UTCVendor advisory
- 2026-08-05 08:20 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 15:02 UTCEG score recompute
- 2026-08-04 15:02 UTCVendor advisory
- 2026-08-04 15:02 UTCGHSA enrichment
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 23:15 UTCEG score recompute
- 2026-08-03 23:15 UTCVendor advisory
- 2026-08-03 23:15 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 10:06 UTCVendor advisory
- 2026-08-03 10:06 UTCGHSA enrichment
- 2026-08-02 20:54 UTCVendor advisory
- 2026-08-02 20:54 UTCGHSA enrichment
- 2026-08-02 07:44 UTCEG score recompute
- 2026-08-02 07:44 UTCVendor advisory
- 2026-08-02 07:44 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-48618?
When was CVE-2026-48618 disclosed?
Is CVE-2026-48618 actively exploited?
What is the CVSS score of CVE-2026-48618?
How do I remediate CVE-2026-48618?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48618
Is Your Infrastructure Affected by CVE-2026-48618?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.