◆ CVE Hub

CVE-2026-105483

Published
2026-10-23
Last modified
2026-10-23
CNA
hackerone
NVD status
Awaiting Analysis
CWE
CWE-295
CVSS v3.1 (listed by NVD)
7.4
HIGH
Scored by hackerone.com (not yet scored by NVD)
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS v4.0 (listed by NVD)
—
Not scored
CVSS (listed by CVE.org)
7.4
HIGH
Scored by CNA (hackerone) · v3.0
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS exploit probability
0.2%
Percentile 14.1%
as of 2026-10-24
CISA KEV
—
Not listed

Attack conditions and impact

Derived from the CNA (via NVD) CVSS 3.0 vector
NetworkNo authNo interactionConditions Confidentiality HIntegrity HAvailability N

This vulnerability may be exploitable over the internet without authentication or user interaction.

MetricValueMeaning
Attack vector AVNNetwork
Attack complexity ACHHigh (conditions required)
Privileges required PRNNone
User interaction UINNone
Scope SUUnchanged
Confidentiality CHHigh
Integrity IHHigh
Availability ANNone
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Description

NVD

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

CVSS assessments

ProviderVersionScoreVector
NVD / [email protected] (Secondary)3.07.4 HIGHCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA / hackerone3.07.4 HIGHCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products and packages

CNA (CVE.org)

VendorProductVersions
nodejsnode
affected: 24.22.0 … <= 24.22.0
affected: 26.12.0 … <= 26.12.0
default: unaffected

Linux distribution status

Red Hat ↗ important

This issue is rated Important. Exploitation requires a Node.js TLS client to connect using a hostname that contains fullwidth Unicode digits which normalize to an IPv4 address, together with a certificate that satisfies the incorrect matching behavior. Attack Complexity is High because the attacker must influence the host string used for the connection (for example a user-supplied URL) and present a suitable certificate, typically with a privileged network position relative to that connection. Confidentiality and Integrity are High because a successful bypass enables server impersonation and exposure or alteration of TLS application data; Availability is not affected. This flaw affects Node.js 24.x and 26.x lines and does not affect the 22.x line per the upstream advisory.

Mitigation: To mitigate do not pass untrusted hostnames that may contain non-ASCII or fullwidth digits into TLS clients such as tls.connect, https.request, or fetch. Restrict outbound TLS connections to trusted destinations only, and segment services that initiate TLS client connections from untrusted networks.

ReleasePackageStatusFixed version / notes
Red Hat Hardened Imageshi/nodejsnot affected
Red Hat Hardened Imagesnodejs20not affected
Red Hat Enterprise Linux 10nodejs22not affected
Red Hat Hardened Imagesnodejs22not affected
Red Hat Enterprise Linux 10nodejs24affected
Red Hat Hardened Imagesnodejs24not affected
Red Hat Hardened Imagesnodejs25will not fix
Red Hat Enterprise Linux 10nodejs26affected
Red Hat Hardened Imagesnodejs26not affected
Red Hat Enterprise Linux 8nodejs:22/nodejsnot affected
Red Hat Enterprise Linux 9nodejs:22/nodejsnot affected
Red Hat Enterprise Linux 8nodejs:24/nodejsaffected
Red Hat Enterprise Linux 9nodejs:24/nodejsaffected
Red Hat Enterprise Linux 9nodejs:26/nodejsaffected

Debian ↗

ReleasePackageStatusFixed version / notes
bookwormnodejsopen not yet assigned
forkynodejsopen not yet assigned
sidnodejsopen not yet assigned
trixienodejsopen not yet assigned

Ubuntu ↗ medium

ReleasePackageStatusFixed version / notes
bionicnodejsneeds-triage
focalnodejsneeds-triage
jammynodejsneeds-triage
noblenodejsneeds-triage
resolutenodejsneeds-triage
stonkingnodejsneeds-triage
trustynodejsneeds-triage
xenialnodejsneeds-triage

References (1)