cve.bz

CVE-2026-106069 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 can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`. `tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.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-106069 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106069?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106069?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-106069 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 22.23.3 through 22.23.3
nodejs nodefrom 24.22.0 through 24.22.0
nodejs nodefrom 26.12.0 through 26.12.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13nodejsno fix listedDEBIAN-CVE-2026-106069
Debian14nodejs24.22.1+dfsg+~cs24.19.2-1DEBIAN-CVE-2026-106069
Ubuntu24.04:LTS, 26.04:LTS, 26.10 and 5 morenodejsno fix listedUBUNTU-CVE-2026-106069
SUSELinux Enterprise Module for Web and Scripting 15 SP7nodejs2222.23.4-150700.3.21.1SUSE-SU-2026:5036-1
SUSELinux Enterprise Module for Web and Scripting 15 SP7nodejs2424.22.1-150700.15.21.1SUSE-SU-2026:5037-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6nodejs2222.23.4-150600.13.27.1SUSE-SU-2026:4957-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0nodejs2222.23.4-160000.1.1SUSE-SU-2026:24600-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.0nodejs2222.23.4-160000.1.1openSUSE-SU-2026:22210-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:22.23.4-2.module_el8.10.0+4358+709b81beALSA-2026:98113
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-nodemon3.1.14-3.module_el8.10.0+4358+709b81beALSA-2026:98113
AlmaLinux8nodejs-packaging, nodejs-packaging-bundler2021.06-6.module_el8.10.0+4086+70facd4aALSA-2026:92376
AlmaLinux8nodejs-packaging, nodejs-packaging-bundler2021.06-6.module_el8.10.0+4158+e796f37fALSA-2026:98113
AlmaLinux8npm1:10.9.9-1.22.23.4.2.module_el8.10.0+4358+709b81beALSA-2026:98113
AlmaLinux8npm1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1ALSA-2026:92376
AlmaLinux8v8-12.4-devel3:12.4.254.21-1.22.23.4.2.module_el8.10.0+4358+709b81beALSA-2026:98113
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
11 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 RLSA-2026:98113
Rocky Linux8nodejs-packaging0:2021.06-6.module+el8.10.0+40171+8fa9c325RLSA-2026:92376 RLSA-2026:98113
Rocky Linux8nodejs-packaging0:2021.06-6.module+el8.10.0+40172+38f6fdd1RLSA-2026:92376 RLSA-2026:98113
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 RLSA-2026:96234
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40052+e32ea525RLSA-2026:92378 RLSA-2026:96234 RLSA-2026:98522
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40153+4d595597RLSA-2026:92378 RLSA-2026:96234 RLSA-2026:98522
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40165+d075e3f2RLSA-2026:92378 RLSA-2026:96234 RLSA-2026:98522
5 more for Rocky Linux in the JSON.
Alpinev3.21, v3.22nodejs22.23.4-r0ALPINE-CVE-2026-106069
Alpinev3.23, v3.24nodejs24.22.1-r0ALPINE-CVE-2026-106069
Alpinev3.24nodejs-current26.12.1-r0ALPINE-CVE-2026-106069
Azure Linux3nodejs24.22.1-0AZL-111047
Alpaquita25nodejs2626.12.1-r0BELL-CVE-2026-106069
Alpaquita25, streamnodejs2222.23.4-r0BELL-CVE-2026-106069
Alpaquita25, streamnodejs2424.22.1-r0BELL-CVE-2026-106069
Alpaquitastreamnodejs2626.12.1-r1BELL-CVE-2026-106069
BellSoft Hardened Containers25nodejs2626.12.1-r0BELL-CVE-2026-106069
BellSoft Hardened Containers25, streamnodejs2222.23.4-r0BELL-CVE-2026-106069
BellSoft Hardened Containers25, streamnodejs2424.22.1-r0BELL-CVE-2026-106069
BellSoft Hardened Containersstreamnodejs2626.12.1-r1BELL-CVE-2026-106069

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 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 · 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 non-canonical numeric hostname that normalizes to an IP address for certificate matching while name resolution uses a different interpretation, and a certificate that includes an IP subjectAltName matching the normalized address. Attack Complexity is High due to these prerequisites and the need to influence the connection target or traffic. Confidentiality and Integrity are High for a successful impersonation of a TLS peer; Availability is not affected. Upstream rates this High and fixed it in Node.js 22.23.4, 24.22.1, and 26.12.1.

Red Hat's mitigation

To mitigate, reject non-canonical numeric hostnames before opening TLS connections. Restrict outbound TLS to trusted destinations only, and isolate services that make TLS client connections based on untrusted input.

--- 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 validate and canonicalize numeric hostnames prior to TLS client connection setup to eliminate normalization discrepancies against the platform resolver: upgrade to Node.js 22.23.4, 24.22.1, 26.12.1 (or the fixed Nodejs/Nodejs:22/Nodejs/Nodejs:24/Nodejs/Nodejs:26/Nodejs/Cloudservices/Subscription Central Automation builds), which reject non-canonical IP addresses during hostname verification, closing all 2 injection vectors (IPv4 literal with leading zero octal notation, abbreviated numeric IPv4 address format). Until patched, this is a concern on Node.js TLS client applications connecting to untrusted hostnames across supported platforms, so reject non-canonical numeric hostnames before initiating TLS connections, restrict outbound TLS requests to trusted destinations, and isolate client services handling untrusted connection targets. As a compensating measure, pin expected server certificates or public keys to reject unauthorized peer certificates even if hostname verification is deceived by address normalization differences. These controls limit blast radius and contain exploitation, but they do not fix the underlying hostname normalization discrepancy defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1304 SSRF Prevention (Outbound Request Allowlist) (high)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10nodejs24-1:24.22.1-3.el10_2Fixed 2026-11-09RHSA-2026:96088
Red Hat Enterprise Linux 10nodejs22-1:22.23.4-1.el10_2Fixed 2026-11-09RHSA-2026:96094
Red Hat Enterprise Linux 8nodejs:24-8100020261027151919.6d880403Fixed 2026-10-29RHSA-2026:92376
Red Hat Enterprise Linux 8nodejs:22-8100020261104150431.6d880403Fixed 2026-11-11RHSA-2026:98113
Red Hat Enterprise Linux 9nodejs:24-9080020261027142403.rhel9Fixed 2026-10-29RHSA-2026:92378
Red Hat Enterprise Linux 9nodejs:22-9080020261103125134.rhel9Fixed 2026-11-09RHSA-2026:96234
Red Hat Enterprise Linux 10nodejs26Affected
Red Hat Enterprise Linux 9nodejs:26/nodejsAffected
Red Hat Hardened Imageshi/nodejsNot affected
Red Hat Hardened Imagesnodejs20Not affected
Red Hat Hardened Imagesnodejs22Not affected
Red Hat Hardened Imagesnodejs24Not affected
Red Hat Hardened Imagesnodejs25Not affected
Red Hat Hardened Imagesnodejs26Not affected

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

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