Quick answers
- Is CVE-2026-105483 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105483 being exploited in the wild.
- How severe is CVE-2026-105483?
- High severity, with a CVSS score of 7.4, published 23 October 2026.
- Which products and versions are affected?
- OpenJS Foundation Node.js 26.x, 24.x.
- Is there a fix for CVE-2026-105483?
- Yes: fixed in Node.js v26.12.1, v24.22.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105483 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105483?
- Check whether you run OpenJS Foundation Node.js at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Node.js v26.12.1, v24.22.1
Technical details
The tls.checkServerIdentity() function fails to recognize IPv4 addresses written with non-ASCII fullwidth digits as IP addresses, and instead matches them against DNS names and Common Name fields in the certificate. An attacker can obtain a certificate with a matching DNS SAN (such as DNS:127.0.0.1 or DNS:*.0.0.1) and use it to authenticate a connection when the client connects to a fullwidth-encoded variant of that IP. This is a regression introduced after CVE-2026-48618.
Affected products
- OpenJS Foundation Node.js 26.x, 24.x
Timeline
- 2026-10-21: disclosed
- 2026-10-23: advisory