nodejs
Affected
- introduced
0(ecosystem)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: CVE-2026-106069
The record has no summary.
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.
High Basis: CVSS v3 score 7.4, vector CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
0 (ecosystem)None listed
No fixed version is listed.
0 (ecosystem)None listed
No fixed version is listed.
0, fixed 24.22.1+dfsg+~cs24.19.2-1 (ecosystem)24.22.1+dfsg+~cs24.19.2-1
24.22.1+dfsg+~cs24.19.2-1sudo apt-get update && sudo apt-get upgradeThis command upgrades the distribution's packages. Compare the fixed version with the version you have installed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: Debian Security Tracker (converted by OSV.dev)
Debian Security Tracker, converted to OSV by OSV.dev.