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**.
Fix
Microsoft's update · Important
- Release Notes — azl3 nodejs 24.21.0-1 on Azure Linux 3.0 · build 24.22.1-0
From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-28.
Public exploits 2
- CompleTetech-Security/node-cve-2026-105483-check PoC on GitHub
- completetech-security/node-cve-2026-105483-check PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Vendor advisories in the News 1
- Node2Shell CVEs Fortinet PSIRT Advisories · 2026-10-26
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 4
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-23 16:15
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-23 19:42
- StatusReceived → PublishedNVD modified 2026-10-23 16:15
- First seenCVSS 7.4NVD modified 2026-10-23 17:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.