{"id":"BIT-node-2026-106069","details":"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`.\n\n`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 authenticated with a certificate issued for another IP address.\n\nThis vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.","aliases":["BIT-node-min-2026-106069","CVE-2026-106069"],"modified":"2026-10-29T10:56:09.337807102Z","published":"2026-10-29T08:55:56.531Z","database_specific":{"severity":"High","cpes":["cpe:2.3:a:nodejs:node.js:*:*:*:*:*:*:*:*"]},"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-106069"}],"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-106069.json"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N"}]}],"schema_version":"1.9.2"}