{"id":"CVE-2026-106072","published":"2026-10-23T17:17:20.203","lastModified":"2026-10-23T19:42:24.553","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`.\n\n`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.\n\nThis vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.","cvssScore":6.7,"cvssSeverity":"MEDIUM","cvssVector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L","cwes":["CWE-295"],"vendors":[],"products":[],"references":[{"url":"https://nodejs.org/en/blog/vulnerability/october-2026-security-releases","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":null}