CVE-2026-106069: CWE-295 Improper Certificate Validation in nodejs node
Description
Node.js versions 22.x, 24.x, and 26.x contain a vulnerability in TLS hostname verification where server certificates can be incorrectly validated against a different IP address when the host is specified as a non-canonical IPv4 literal with leading zeros. This occurs because the hostname normalization interprets leading-zero octets as octal, while the OS resolver interprets them as decimal, potentially allowing a server to be authenticated with a certificate issued for another IP address.
CVSS v3.0
Score 7.4high
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-106069 describes an improper certificate validation vulnerability in Node.js TLS hostname verification. The function tls.checkServerIdentity() normalizes hostnames following WHATWG URL rules, interpreting leading-zero octets in IPv4 addresses as octal numbers (e.g., '0127.0.0.1' becomes '87.0.0.1'). However, the operating system resolver, such as on macOS, interprets these octets as decimal (e.g., '127.0.0.1'). This mismatch can cause a server certificate to be validated against an IP address different from the one the client connected to, allowing a server at the connected address to be authenticated with a certificate issued for another IP address. The vulnerability affects Node.js versions 22.23.3, 24.22.0, and 26.12.0.
Potential Impact
This vulnerability can lead to a high-severity impact where a client may incorrectly trust a server certificate that does not match the actual server IP address it connected to. This undermines the TLS authentication process, potentially enabling man-in-the-middle attacks or impersonation of trusted servers.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Users should monitor Node.js vendor advisories for updates addressing this issue and avoid using non-canonical IPv4 literals with leading zeros in hostnames until a fix is available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-10-06T15:00:00.654Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 6adb8965d73cc49347a5c6e6
Added to database: 10/23/2026, 16:20:53 UTC
Last enriched: 10/23/2026, 16:35:09 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.