CVE-2026-106072: CWE-295 Improper Certificate Validation in nodejs node
Description
Node.js versions 22.23.3, 24.22.0, and 26.12.0 contain a vulnerability in TLS hostname verification where certificates with only a DNS Subject Alternative Name (SAN) can authenticate IP endpoints if the client uses non-canonical IPv4 address spellings. This occurs because tls.checkServerIdentity() normalizes these addresses and matches them against DNS names, allowing improper validation. Exploitation requires a trusted CA to issue a certificate with a numeric DNS SAN and a platform resolver that accepts non-canonical IP formats.
CVSS v3.0
Score 6.7medium
Affected software
nodejs
node
pkg:npm/nodeRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-106072 is a vulnerability in Node.js TLS hostname verification (CWE-295) affecting versions 22.23.3, 24.22.0, and 26.12.0. The flaw allows a certificate containing only a DNS SAN with a numeric IP address to authenticate an IP endpoint when the client connects using non-canonical IPv4 spellings such as octal, hexadecimal, or integer formats. The function tls.checkServerIdentity() fails to classify these hosts as IP addresses and instead normalizes them to canonical form and matches against DNS names. This leads to acceptance of certificates with DNS:127.0.0.1 but no IP Address SAN for 127.0.0.1, which should be rejected. Exploitation requires a certificate from a trusted CA and a platform resolver like glibc that accepts these non-canonical IP spellings.
Potential Impact
Successful exploitation allows an attacker with a certificate containing a numeric DNS SAN issued by a trusted CA to impersonate an IP endpoint when clients connect using non-canonical IPv4 address formats. This can lead to a high impact on confidentiality and integrity, as TLS connections may be improperly authenticated. Availability impact is low. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using non-canonical IPv4 address formats when connecting to TLS endpoints in affected Node.js versions. Monitor vendor channels for updates and apply patches once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-10-06T15:00:00.655Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 6adb8965d73cc49347a5c6e9
Added to database: 10/23/2026, 16:20:53 UTC
Last enriched: 10/23/2026, 16:35:33 UTC
Last updated: 10/23/2026, 16:35:52 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.