CVE-2026-105483: high-severity vulnerability in nodejs node
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 7.4epss 0.3%
from disclosure to weaponsame day
Published on NVDOct 23
1st PoCOct 23
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`１２７.0.0.1`).
`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.
This vulnerability affects Node.js **26.x** and **24.x**.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected products
nodejs · nodepublic PoCs found — 4
githubgithub.com/CompleTetech-Security/node-cve-2026-105483-check★ 0githubgithub.com/CompleteTech-LLC/node-cve-2026-105483-check★ 0githubgithub.com/CompleTech-Security/node-cve-2026-105483-check★ 0githubgithub.com/CompleteTech-Security/node-cve-2026-105483-check★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — nodejs node
In the same product, most dangerous first.