CVE-2026-105483

HIGH
MEDIUM Priority: 0.02 BB Relevance: 65/100
Published: 2026-10-23 Modified: 2026-10-23 First seen: 2026-10-29 Status: active

Attack Surface

Network No Auth No Interaction Conf. Impact Integ. Impact

CVSS Vector Breakdown

AV: Network
AC: High
PR: None
UI: None
S: Unchanged
C: High
I: High
A: None

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 (`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**.

Weakness Classification (1)

Bug Bounty Relevance

65 / 100
✓ Network accessible
✓ No authentication
✓ No user interaction

CVSS Score

7.4 / 10.0 v3.0
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS — Exploitation Probability

0.30%
Raw Score 0.003040
Percentile 23.2%
Date 2026-10-29

EPSS Trend

2026-10-29
0.00304
2026-10-28
0.00275

Intelligence Sources

nvd ref →