Node.js TLS hostname verification bypass with leading-zero IPv4
CVE-2026-106069High
Node.js TLS hostname verification normalises IPv4 addresses with leading zeros using WHATWG URL rules, which interpret them as octal notation, whilst the operating system resolver on some platforms interprets them as decimal. An attacker who controls a server at the decimal interpretation of the address can present a certificate issued for the octal interpretation and successfully authenticate, because the two addresses are treated as equivalent during verification when they are not.
Plain English summary of the NVD and CISA text, checked by machine against both.
Scores and dates
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Detail
Reports naming this CVE5 in total
· Cisco Security Advisory
Vulnerabilities in Node.js and Brotli Affecting Cisco Products: October 2026 (opens in a new tab)· Cisco Security Advisory
Vulnerabilities in Node.js Affecting Cisco Products: October 2026 (opens in a new tab)· Qualys Security Blog
Waiting on a Node.js Upgrade? Build a Stopgap with the Controls You Own (opens in a new tab)· Cisco Security Advisory
Vulnerabilities in node.js Affecting Cisco Products: October 2026 (opens in a new tab)· FortiGuard Labs IR Advisories
Multiple Node.js CVEs (opens in a new tab)