{"id":"BIT-node-2026-106072","details":"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**.","aliases":["BIT-node-min-2026-106072","CVE-2026-106072"],"modified":"2026-10-29T10:56:15.644460092Z","published":"2026-10-29T08:56:00.617Z","database_specific":{"cpes":["cpe:2.3:a:nodejs:node.js:*:*:*:*:*:*:*:*"],"severity":"Medium"},"references":[{"type":"WEB","url":"https://nodejs.org/en/blog/vulnerability/october-2026-security-releases"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-106072"}],"affected":[{"package":{"name":"node","ecosystem":"Bitnami","purl":"pkg:bitnami/node"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"22.23.4"},{"introduced":"23.0.0"},{"fixed":"24.22.1"},{"introduced":"25.0.0"},{"fixed":"26.12.1"}]}],"database_specific":{"source":"https://github.com/bitnami/vulndb/tree/main/data/node/BIT-node-2026-106072.json"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L"}]}],"schema_version":"1.9.2"}