CVE-2026-48618
Last modified
CVE-2026-48618 is a medium-severity vulnerability rated 6.5/10 on the CVSS scale. 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**.. EPSS estimates a 0.61% chance of exploitation in the next 30 days.
Description
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**.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Nodejs | Node.Js | 22.22.3 |
| Nodejs | Node.Js | 24.16.0 |
| Nodejs | Node.Js | 26.3.0 |
References
- https://nodejs.org/en/blog/vulnerability/june-2026-security-releasesPatch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-48618?
How severe is CVE-2026-48618?
How do I fix CVE-2026-48618?
Are you affected by CVE-2026-48618?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
