Nodejs node
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 (`127.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**.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 24.22.0, <= 24.22.0
- >= 26.12.0, <= 26.12.0
Mitigation
The record names no fix. Check the vendor advisory below.
Timeline
Days relative to CVE publicationFirst public PoC 8 h after publication; not in CISA KEV. First PoC: CompleTech-Security/node-cve-2026-105483-check (created 23 Oct 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.2 PoCs
PoCs 2
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| CompleTech-Security/node-cve-2026-105483-check | 23 Oct 2026 +8 h | 14 Nov 2026 | 0 | Scanner
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
| completetech-security/node-cve-2026-105483-check | 23 Oct 2026 +8 h | 14 Nov 2026 | 0 | Scanner
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.