Nodejs node
A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`. `tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 22.23.3, <= 22.23.3
- >= 24.22.0, <= 24.22.0
- >= 26.12.0, <= 26.12.0
Mitigation
The record names no fix. Check the vendor advisory below.
Timeline
Days relative to CVE publicationFirst public PoC 8 h after publication; not in CISA KEV. First PoC: CompleTech-Security/node-cve-2026-106069-check (created 23 Oct 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.2 PoCs
PoCs 2
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| CompleTech-Security/node-cve-2026-106069-check | 23 Oct 2026 +8 h | 14 Nov 2026 | 0 | Scanner
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
| completetech-security/node-cve-2026-106069-check | 23 Oct 2026 +8 h | 14 Nov 2026 | 0 | Scanner
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.