CVE-2026-105483 A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 a
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-105483?
CVE-2026-105483 is a high-severity vulnerability in nodejs node, published on 23 Oct 2026.
Official description
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**.
Weakness: CWE-295
Which versions are affected by CVE-2026-105483?
2 open source packages ship an affected version, including node and node-min.
| Package | Affected | Fixed in |
|---|---|---|
node Bitnami | From 23.0.0 | 24.22.1, 26.12.1 |
node-min Bitnami | From 23.0.0 | 24.22.1, 26.12.1 |
How do I fix CVE-2026-105483?
Upgrade node to a fixed version for your release line: 24.22.1 or 26.12.1.
Is CVE-2026-105483 being exploited?
There is no known exploitation of CVE-2026-105483 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as ALPINE-CVE-2026-105483, AZL-111038, BIT-node-2026-105483, BIT-node-min-2026-105483, DEBIAN-CVE-2026-105483, GHSA-8h4p-qpcq-gq24 and 1 more.