CVE-2026-48618
Node.js TLS Hostname Normalization Bypass
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**.
INFO
Published Date :
June 26, 2026, 1:14 a.m.
Last Modified :
June 26, 2026, 1:14 a.m.
Remotely Exploit :
No
Source :
hackerone
Affected Products
The following products are affected by CVE-2026-48618
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update Node.js to the latest patched version.
- Apply relevant security patches for Node.js.
- Restart affected Node.js processes.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-48618 vulnerability anywhere in the article.