| Name | CVE-2026-106069 |
| Description | 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`. `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. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. |
| Source | CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| Debian Bugs | 1151688, 1151859 |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| nodejs (PTS) | bookworm | 18.20.4+dfsg-1~deb12u2 | vulnerable |
| bookworm (security) | 18.20.4+dfsg-1~deb12u3 | vulnerable | |
| trixie | 20.19.2+dfsg-1+deb13u2 | vulnerable | |
| trixie (security) | 20.19.2+dfsg-1+deb13u3 | vulnerable | |
| forky, sid | 24.22.2+dfsg+~cs24.19.2-1 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| nodejs | source | (unstable) | 24.22.1+dfsg+~cs24.19.2-1 | 1151688, 1151859 |
https://nodejs.org/en/blog/vulnerability/october-2026-security-releases#tls-certificate-hostname-bypass-when-the-host-loosely-resolves-to-an-ip-address-cve-2026-106069---high
Fixed by: https://github.com/nodejs/node/commit/d7663560ac9e7bb4ddd659e3120c99a55490f18d (v22.23.4)