{"id":"CVE-2026-106072","revision":"8163bca81f854048924d42fb2fd961e7","records":[{"revision":"8163bca81f854048924d42fb2fd961e7","observedAt":"2026-10-23T17:48:20.538+00:00","statement":{"source":"cve-program","id":"CVE-2026-106072","aliases":[],"title":"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`.","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**.","state":0,"publishedAt":"2026-10-23T16:15:05.783+00:00","modifiedAt":"2026-10-23T16:15:05.783+00:00","affected":[{"ecosystem":"Vendor product","name":"node","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"defaultStatus\": \"unaffected\",\n                    \"vendor\": \"nodejs\",\n                    \"product\": \"node\",\n                    \"versions\": [\n                        {\n                            \"version\": \"22.23.3\",\n                            \"status\": \"affected\",\n                            \"lessThanOrEqual\": \"22.23.3\",\n                            \"versionType\": \"semver\"\n                        },\n                        {\n                            \"version\": \"24.22.0\",\n                            \"status\": \"affected\",\n                            \"lessThanOrEqual\": \"24.22.0\",\n                            \"versionType\": \"semver\"\n                        },\n                        {\n                            \"version\": \"26.12.0\",\n                            \"status\": \"affected\",\n                            \"lessThanOrEqual\": \"26.12.0\",\n                            \"versionType\": \"semver\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.0","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L","score":6.7,"severity":"MEDIUM"}],"references":["https://nodejs.org/en/blog/vulnerability/october-2026-security-releases"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-106072","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-106072","identifiers":["CVE-2026-106072"]},"retained":false,"historicalAffected":[]}],"coverage":[]}