cve.bz

CVE-2026-105483 nodejs node: Improper Certificate Validation

7.4 highEPSS 0.3%

High (7.4) in nodejs node. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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**.

Severity

CVSS 3.0

7.4 high
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105483 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105483?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105483?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105483 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nodejs nodefrom 24.22.0 through 24.22.0
nodejs nodefrom 26.12.0 through 26.12.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14nodejs24.22.1+dfsg+~cs24.19.2-1DEBIAN-CVE-2026-105483
Ubuntu24.04:LTS, 26.04:LTS, 26.10 and 5 morenodejsno fix listedUBUNTU-CVE-2026-105483
Red Hathummingbird:1nodejs22, nodejs22-bin, nodejs22-docs and 4 more1:22.23.4-2.3.2.3.hum1RHSA-2026:87702
Red Hathummingbird:1nodejs22-npm1:10.9.9-1.22.23.4.2.3.2.3.hum1RHSA-2026:87702
Red Hathummingbird:1nodejs24, nodejs24-bin, nodejs24-docs and 3 more1:24.22.1-3.hum1RHSA-2026:89206
Red Hathummingbird:1nodejs24-npm2:11.19.1-1.24.22.1.3.hum1RHSA-2026:89206
Red Hathummingbird:1nodejs24-npm-bin2:24.22.1-3.hum1RHSA-2026:89206
Red Hathummingbird:1nodejs26, nodejs26-bin, nodejs26-docs and 4 more1:26.12.1-0.1.hum1RHSA-2026:87703
Red Hathummingbird:1nodejs26-npm1:11.20.0-1.26.12.1.0.1.hum1RHSA-2026:87703
SUSELinux Enterprise Module for Web and Scripting 15 SP7nodejs2424.22.1-150700.15.21.1SUSE-SU-2026:5037-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0nodejs2424.22.1-160000.1.1SUSE-SU-2026:24732-1
SUSELinux Enterprise Server 16.1, Linux Enterprise Server for SAP applications 16.1nodejs2424.22.1-160100.1.1SUSE-SU-2026:24548-1
SUSELinux Enterprise Server for NVIDIA 16.1nodejs2424.22.1-160100.1.1SUSE-SU-2026:24696-1
openSUSELeap 16.1nodejs2424.22.1-160100.1.1openSUSE-SU-2026:22292-1
openSUSETumbleweednodejs2424.22.1-1.1openSUSE-SU-2026:12248-1
AlmaLinux8nodejs, nodejs-docs, nodejs-libs and 2 more1:24.22.1-1.module_el8.10.0+4331+0683c9c1ALSA-2026:92376
AlmaLinux8nodejs-nodemon3.1.14-2.module_el8.10.0+4250+09238ed4ALSA-2026:92376
AlmaLinux8nodejs-packaging, nodejs-packaging-bundler2021.06-6.module_el8.10.0+4086+70facd4aALSA-2026:92376
AlmaLinux8npm1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1ALSA-2026:92376
AlmaLinux8v8-13.6-devel3:13.6.233.17-1.24.22.1.1.module_el8.10.0+4331+0683c9c1ALSA-2026:92376
AlmaLinux9nodejs, nodejs-docs, nodejs-libs and 2 more1:24.22.1-3.module_el9.8.0+333+788f3075ALSA-2026:92378
AlmaLinux9nodejs, nodejs-docs, nodejs-libs and 2 more1:26.12.1-2.module_el9.9.0+350+dfbd8996ALSA-2026:98522
AlmaLinux9nodejs-nodemon3.1.14-2.module_el9.9.0+304+ff00f651ALSA-2026:98522
AlmaLinux9nodejs-nodemon3.1.14-3.module_el9.8.0+292+f4eaf8b2ALSA-2026:92378
AlmaLinux9nodejs-packaging, nodejs-packaging-bundler2021.06-6.module_el9.7.0+209+ecf6523eALSA-2026:92378
AlmaLinux9nodejs-packaging, nodejs-packaging-bundler2021.06-6.module_el9.9.0+304+ff00f651ALSA-2026:98522
AlmaLinux9npm1:11.19.1-1.24.22.1.3.module_el9.8.0+333+788f3075ALSA-2026:92378
4 more for AlmaLinux in the JSON.
Rocky Linux8nodejs-nodemon0:3.1.14-2.module+el8.10.0+40277+b1b3f89eRLSA-2026:92376
Rocky Linux8nodejs-nodemon0:3.1.14-2.module+el8.10.0+40278+50b003a3RLSA-2026:92376
Rocky Linux8nodejs-packaging0:2021.06-6.module+el8.10.0+40048+6d99f608RLSA-2026:92376
Rocky Linux8nodejs-packaging0:2021.06-6.module+el8.10.0+40171+8fa9c325RLSA-2026:92376
Rocky Linux8nodejs-packaging0:2021.06-6.module+el8.10.0+40172+38f6fdd1RLSA-2026:92376
Rocky Linux9nodejs1:24.22.1-3.module+el9.8.0+40401+e24b8c95RLSA-2026:92378
Rocky Linux9nodejs-nodemon0:3.1.14-2.module+el9.8.0+40264+d9b257bbRLSA-2026:98522
Rocky Linux9nodejs-nodemon0:3.1.14-2.module+el9.8.0+40280+057606e8RLSA-2026:98522
Rocky Linux9nodejs-nodemon0:3.1.14-3.module+el9.8.0+40281+14cc6568RLSA-2026:92378
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40052+e32ea525RLSA-2026:92378 RLSA-2026:98522
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40153+4d595597RLSA-2026:92378 RLSA-2026:98522
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40165+d075e3f2RLSA-2026:92378 RLSA-2026:98522
4 more for Rocky Linux in the JSON.
Alpinev3.23, v3.24nodejs24.22.1-r0ALPINE-CVE-2026-105483
Alpinev3.24nodejs-current26.12.1-r0ALPINE-CVE-2026-105483
Azure Linux3nodejs24.22.1-0AZL-111038
Alpaquita25nodejs2626.12.1-r0BELL-CVE-2026-105483
Alpaquita25, streamnodejs2424.22.1-r0BELL-CVE-2026-105483
Alpaquitastreamnodejs2626.12.1-r1BELL-CVE-2026-105483
BellSoft Hardened Containers25nodejs2626.12.1-r0BELL-CVE-2026-105483
BellSoft Hardened Containers25, streamnodejs2424.22.1-r0BELL-CVE-2026-105483
BellSoft Hardened Containersstreamnodejs2626.12.1-r1BELL-CVE-2026-105483

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Important.

Red Hat's statement

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.

Red Hat's 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.

--- CME Mitigation Guidance (2026-11-02) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to normalize hostnames and IP representations to standard ASCII before passing destination strings to TLS client calls such as tls.connect, https.request, or fetch: upgrade to Node.js v24.22.1, v26.12.1 (or the fixed Nodejs/Nodejs:24/Nodejs/Nodejs:26/Nodejs/Cloudservices/Subscription Central Automation builds), which fix IP normalization regression in TLS hostname validation to ensure fullwidth digit hostnames are recognized as IP addresses, closing all 2 injection vectors (fullwidth Unicode digit IPv4 connection strings, DNS SAN matching on numeric hostnames). Until patched, this is only a concern on Node.js applications running on 24.x and 26.x runtimes establishing TLS client connections — Node.js 22.x deployments are unaffected — so Do not pass untrusted hostnames or URLs that may contain non-ASCII or fullwidth digits into TLS clients, and restrict outbound TLS connections to trusted destinations. As a compensating measure, Restrict outbound requests to a validated destination allowlist to prevent arbitrary attacker-controlled host strings from reaching Node.js TLS clients and Segment services initiating TLS client connections from untrusted networks to prevent attackers from intercepting or impersonating connections. These controls limit blast radius and contain exploitation, but they do not fix the underlying TLS IP hostname normalization defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1315 Allowlist-Preferred Input Validation (Deny-by-Default Filtering) (high)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10nodejs24-1:24.22.1-3.el10_2Fixed 2026-11-09RHSA-2026:96088
Red Hat Enterprise Linux 8nodejs:24-8100020261027151919.6d880403Fixed 2026-10-29RHSA-2026:92376
Red Hat Enterprise Linux 9nodejs:24-9080020261027142403.rhel9Fixed 2026-10-29RHSA-2026:92378
Red Hat Hardened Imagesnodejs22-main-10.9.9-1.22.23.4.2.3.2.3.hum1Fixed 2026-10-22RHSA-2026:87702
Red Hat Hardened Imagesnodejs22-main-22.23.4-2.3.2.3.hum1Fixed 2026-10-22RHSA-2026:87702
Red Hat Hardened Imagesnodejs26-main-11.20.0-1.26.12.1.0.1.hum1Fixed 2026-10-22RHSA-2026:87703
Red Hat Hardened Imagesnodejs26-main-26.12.1-0.1.hum1Fixed 2026-10-22RHSA-2026:87703
Red Hat Hardened Imagesnodejs24-main-11.19.1-1.24.22.1.3.hum1Fixed 2026-10-25RHSA-2026:89206
Red Hat Hardened Imagesnodejs24-main-24.22.1-3.hum1Fixed 2026-10-25RHSA-2026:89206
Red Hat Enterprise Linux 10nodejs22Not affected
Red Hat Enterprise Linux 10nodejs26Affected
Red Hat Enterprise Linux 8nodejs:22/nodejsNot affected
Red Hat Enterprise Linux 9nodejs:22/nodejsNot affected
Red Hat Enterprise Linux 9nodejs:26/nodejsAffected
Red Hat Hardened Imageshi/nodejsNot affected
Red Hat Hardened Imagesnodejs20Not affected
Red Hat Hardened Imagesnodejs25Will not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105483.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON