A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.
CVE-2026-48930
Score 5.6 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 9.8; sources differ by 4.2.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 5.6(medium)
- EPSS
- 32.5%
- KEV
- Not listed
Published
June 26, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 29, 2026Node.js — Thursday, June 18, 2026 Security Releases
https://nodejs.org/en/blog/vulnerability/june-2026-security-releasesVendor Advisories for CVE-2026-48930(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | nodejs24-1:24.18.0-1.el10_2 | 2026-07-06 | redhat |
| redhat | nodejs22-1:22.23.1-2.el10_2 | 2026-07-06 | 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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
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 22× in last 7d / 37× 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.
- 2026-07-06 17:33 UTCEG score recompute
- 2026-07-06 17:33 UTCVendor advisory
- 2026-07-06 17:32 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 16:10 UTCEG score recompute
- 2026-07-05 16:09 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 14:48 UTCEG score recompute
- 2026-07-04 14:48 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 13:26 UTCEG score recompute
- 2026-07-03 13:26 UTCGHSA enrichment
- 2026-07-02 12:04 UTCEG score recompute
- 2026-07-02 12:04 UTCGHSA enrichment
- 2026-07-02 12:02 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 10:40 UTCEG score recompute
- 2026-07-01 10:40 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 09:18 UTCEG score recompute
- 2026-06-30 09:18 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 07:56 UTCEG score recompute
Show 12 moreShow fewer
- 2026-06-29 07:56 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 06:30 UTCEG score recompute
- 2026-06-28 06:30 UTCGHSA enrichment
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 05:09 UTCEG score recompute
- 2026-06-27 05:08 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 21:42 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
- 2026-06-26 03:46 UTCEG score recompute
- 2026-06-26 03:46 UTCGHSA enrichment
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-284
Frequently asked(5)
What is CVE-2026-48930?
When was CVE-2026-48930 disclosed?
Is CVE-2026-48930 actively exploited?
What is the CVSS score of CVE-2026-48930?
How do I remediate CVE-2026-48930?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-48930
Is Your Infrastructure Affected by CVE-2026-48930?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.