CVE-2026-106069: high-severity vulnerability in nodejs node
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 7.4epss 0.3%
from disclosure to weaponsame day
Published on NVDOct 23
1st PoCOct 23
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**.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected products
nodejs · nodepublic PoCs found — 4
githubgithub.com/CompleteTech-LLC/node-cve-2026-106069-check★ 0githubgithub.com/CompleTech-Security/node-cve-2026-106069-check★ 0githubgithub.com/CompleTetech-Security/node-cve-2026-106069-check★ 0githubgithub.com/CompleteTech-Security/node-cve-2026-106069-check★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — nodejs node
In the same product, most dangerous first.