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**.
Affected products
nodejs: node.js
References10
- nodejs.org/en/blog/vulnerability/june-2026-security-releases PatchVendor Advisory
- access.redhat.com/errata/RHSA-2026:28727
- access.redhat.com/errata/RHSA-2026:29012
- access.redhat.com/errata/RHSA-2026:30172
- access.redhat.com/errata/RHSA-2026:35841
- access.redhat.com/errata/RHSA-2026:35842
- access.redhat.com/errata/RHSA-2026:35891
- access.redhat.com/errata/RHSA-2026:35892
- access.redhat.com/errata/RHSA-2026:39246
- access.redhat.com/errata/RHSA-2026:39868
Metrics
- CVSS 3.1
-
6.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 3% percentile: 88 · as of 16 November 2026
- CWE
- CWE-176CWE-289
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.