Skip to content
fr Sign in
6.7 Medium

CVE-2026-106072 A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when…

Description

A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`. `tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

Affected products and versions

Product Affected versions Fixed in
Node 26.12.0 No fix stated
Node 24.22.0 No fix stated
Node 22.23.3 No fix stated

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Node

The 129 CVEs of Node →
CVE-2026-106073 A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read… 3.3 Low CVE-2026-106069 A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP… 7.4 High CVE-2026-106070 A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after… 3.7 Low CVE-2026-106071 A flaw in Node.js Permission Model filesystem enforcement can grant access to paths that do not match a wildcard… 3.6 Low
Track this CVE