CVE-2026-105483A 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,…
Updated under an hour ago ()
Does this affect you?
It affects nodejs node. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.27%, higher than 20% of scored CVEs.
Do this next
Free account, 1 product
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
- 7.4 HIGH (v3.0, CNA)CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Weakness (CWE)
- CWE-295
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.27% (percentile 20)
- Assigned by
- hackerone
- NVD analysis
- Awaiting Analysis
- Record last updated
- Oct 23, 2026
- First seen by InfoSec Signals
- Oct 23, 2026
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.