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…
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 authent
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Apple, Canonical
- Product
- macos, canonical
- CVSS
- 7.4
- EPSS
- 0.003 (p23)
- Exposure class
- Developer platform, Operating system
Why it ranks 27 (Notable)
- CVSS 7.4 high
- Product class: developer platform, operating system
- Covered by 3 independent sources
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.
Links
- NIST National Vulnerability Database (CVE API 2.0) (nvd.nist.gov)
- CVE-2026-106069 on this site · NVD · CVE.org · Vulnpedia
Related coverage
Other items that share a CVE or were clustered with this one.