CVE-2026-106069
Node.js: TLS certificate validated against a different IP than the one connected to
Technology
Node.js
CVSS Score
7.4 / 10.0
Affected Versions
>=22.0.0 <22.23.4; >=24.0.0 <24.22.1; >=26.0.0 <26.12.1
Upstream Fix
22.23.4; 24.22.1; 26.12.1
Published
October 23, 2026
OSSeva Coverage
Fixed upstream
Description
For a non-canonical IPv4 literal with a leading zero, such as 0127.0.0.1, tls.checkServerIdentity() follows the WHATWG URL rules and reads the octet as octal (87.0.0.1), while the connection goes 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. Rated High by Node.js; the score is the CNA's, as NVD had not yet analysed the record. Fixed in 22.23.4, 24.22.1 and 26.12.1.
Is your Node.js deployment affected?
If you're running >=22.0.0 <22.23.4; >=24.0.0 <24.22.1; >=26.0.0 <26.12.1, you need this patch. Book a discovery call to get covered.
Get a quote
Running Node.js >=22.0.0 <22.23.4; >=24.0.0 <24.22.1; >=26.0.0 <26.12.1?
Send your work email and a senior engineer will tell you whether this CVE applies to your versions and who patches it. Reply within 1 business day.
Prefer to talk or read more first?