Node.js TLS hostname verification
Affects nodeSource GCVE Database
Not known to be exploited · CVSS 6.7 Medium · fixed in 26.12.1 : update node when convenient.
Data as of 29 Oct 2026, 13:18 UTC
Thin evidence
One scorer or none| CNA (hackerone) | CVSS 3.0 | 6.7 |
|---|
- Patch
- Available – fixed in 26.12.1, 24.22.1, 22.23.4
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade node to 26.12.1, 24.22.1 or 22.23.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnaminodepkg:bitnami/nodeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability has been fixed in Node.js versions 22.23.4, 24.22.1, and 26.12.1. Users should upgrade affected Node.js versions to these or later releases to remediate the issue. No other mitigation is required as the fix addresses the root cause in TLS hostname verification.
Description
A vulnerability in Node.js TLS hostname verification allows a certificate with only a DNS Subject Alternative Name (SAN) containing a numeric IP address to authenticate an IP endpoint when the client connects using non-canonical IPv4 address formats. This occurs because the function tls.checkServerIdentity() normalizes non-canonical IP addresses to their canonical form and matches them against DNS names in the certificate, incorrectly accepting certificates with DNS SANs for numeric IPs. The flaw affects Node.js versions 22.x, 24.x, and 26.x prior to specific fixed releases.