CVSS 3.0
7.4 highCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NHigh (7.4) in nodejs node. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| nodejs node | from 22.23.3 through 22.23.3 |
| nodejs node | from 24.22.0 through 24.22.0 |
| nodejs node | from 26.12.0 through 26.12.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | nodejs | no fix listed | DEBIAN-CVE-2026-106069 |
| Debian | 14 | nodejs | 24.22.1+dfsg+~cs24.19.2-1 | DEBIAN-CVE-2026-106069 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 and 5 more | nodejs | no fix listed | UBUNTU-CVE-2026-106069 |
| SUSE | Linux Enterprise Module for Web and Scripting 15 SP7 | nodejs22 | 22.23.4-150700.3.21.1 | SUSE-SU-2026:5036-1 |
| SUSE | Linux Enterprise Module for Web and Scripting 15 SP7 | nodejs24 | 24.22.1-150700.15.21.1 | SUSE-SU-2026:5037-1 |
| SUSE | Linux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6 | nodejs22 | 22.23.4-150600.13.27.1 | SUSE-SU-2026:4957-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | nodejs22 | 22.23.4-160000.1.1 | SUSE-SU-2026:24600-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | nodejs24 | 24.22.1-160000.1.1 | SUSE-SU-2026:24732-1 |
| SUSE | Linux Enterprise Server 16.1, Linux Enterprise Server for SAP applications 16.1 | nodejs24 | 24.22.1-160100.1.1 | SUSE-SU-2026:24548-1 |
| SUSE | Linux Enterprise Server for NVIDIA 16.1 | nodejs24 | 24.22.1-160100.1.1 | SUSE-SU-2026:24696-1 |
| openSUSE | Leap 16.0 | nodejs22 | 22.23.4-160000.1.1 | openSUSE-SU-2026:22210-1 |
| openSUSE | Leap 16.1 | nodejs24 | 24.22.1-160100.1.1 | openSUSE-SU-2026:22292-1 |
| openSUSE | Tumbleweed | nodejs24 | 24.22.1-1.1 | openSUSE-SU-2026:12248-1 |
| AlmaLinux | 8 | nodejs, nodejs-docs, nodejs-libs and 2 more | 1:22.23.4-2.module_el8.10.0+4358+709b81be | ALSA-2026:98113 |
| AlmaLinux | 8 | nodejs, nodejs-docs, nodejs-libs and 2 more | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 | ALSA-2026:92376 |
| AlmaLinux | 8 | nodejs-nodemon | 3.1.14-2.module_el8.10.0+4250+09238ed4 | ALSA-2026:92376 |
| AlmaLinux | 8 | nodejs-nodemon | 3.1.14-3.module_el8.10.0+4358+709b81be | ALSA-2026:98113 |
| AlmaLinux | 8 | nodejs-packaging, nodejs-packaging-bundler | 2021.06-6.module_el8.10.0+4086+70facd4a | ALSA-2026:92376 |
| AlmaLinux | 8 | nodejs-packaging, nodejs-packaging-bundler | 2021.06-6.module_el8.10.0+4158+e796f37f | ALSA-2026:98113 |
| AlmaLinux | 8 | npm | 1:10.9.9-1.22.23.4.2.module_el8.10.0+4358+709b81be | ALSA-2026:98113 |
| AlmaLinux | 8 | npm | 1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 | ALSA-2026:92376 |
| AlmaLinux | 8 | v8-12.4-devel | 3:12.4.254.21-1.22.23.4.2.module_el8.10.0+4358+709b81be | ALSA-2026:98113 |
| AlmaLinux | 8 | v8-13.6-devel | 3:13.6.233.17-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 | ALSA-2026:92376 |
| AlmaLinux | 9 | nodejs, nodejs-docs, nodejs-libs and 2 more | 1:24.22.1-3.module_el9.8.0+333+788f3075 | ALSA-2026:92378 |
| AlmaLinux | 9 | nodejs, nodejs-docs, nodejs-libs and 2 more | 1:26.12.1-2.module_el9.9.0+350+dfbd8996 | ALSA-2026:98522 |
| 11 more for AlmaLinux in the JSON. | ||||
| Rocky Linux | 8 | nodejs-nodemon | 0:3.1.14-2.module+el8.10.0+40277+b1b3f89e | RLSA-2026:92376 |
| Rocky Linux | 8 | nodejs-nodemon | 0:3.1.14-2.module+el8.10.0+40278+50b003a3 | RLSA-2026:92376 |
| Rocky Linux | 8 | nodejs-packaging | 0:2021.06-6.module+el8.10.0+40048+6d99f608 | RLSA-2026:92376 RLSA-2026:98113 |
| Rocky Linux | 8 | nodejs-packaging | 0:2021.06-6.module+el8.10.0+40171+8fa9c325 | RLSA-2026:92376 RLSA-2026:98113 |
| Rocky Linux | 8 | nodejs-packaging | 0:2021.06-6.module+el8.10.0+40172+38f6fdd1 | RLSA-2026:92376 RLSA-2026:98113 |
| Rocky Linux | 9 | nodejs | 1:24.22.1-3.module+el9.8.0+40401+e24b8c95 | RLSA-2026:92378 |
| Rocky Linux | 9 | nodejs-nodemon | 0:3.1.14-2.module+el9.8.0+40264+d9b257bb | RLSA-2026:98522 |
| Rocky Linux | 9 | nodejs-nodemon | 0:3.1.14-2.module+el9.8.0+40280+057606e8 | RLSA-2026:98522 |
| Rocky Linux | 9 | nodejs-nodemon | 0:3.1.14-3.module+el9.8.0+40281+14cc6568 | RLSA-2026:92378 RLSA-2026:96234 |
| Rocky Linux | 9 | nodejs-packaging | 0:2021.06-6.module+el9.7.0+40052+e32ea525 | RLSA-2026:92378 RLSA-2026:96234 RLSA-2026:98522 |
| Rocky Linux | 9 | nodejs-packaging | 0:2021.06-6.module+el9.7.0+40153+4d595597 | RLSA-2026:92378 RLSA-2026:96234 RLSA-2026:98522 |
| Rocky Linux | 9 | nodejs-packaging | 0:2021.06-6.module+el9.7.0+40165+d075e3f2 | RLSA-2026:92378 RLSA-2026:96234 RLSA-2026:98522 |
| 5 more for Rocky Linux in the JSON. | ||||
| Alpine | v3.21, v3.22 | nodejs | 22.23.4-r0 | ALPINE-CVE-2026-106069 |
| Alpine | v3.23, v3.24 | nodejs | 24.22.1-r0 | ALPINE-CVE-2026-106069 |
| Alpine | v3.24 | nodejs-current | 26.12.1-r0 | ALPINE-CVE-2026-106069 |
| Azure Linux | 3 | nodejs | 24.22.1-0 | AZL-111047 |
| Alpaquita | 25 | nodejs26 | 26.12.1-r0 | BELL-CVE-2026-106069 |
| Alpaquita | 25, stream | nodejs22 | 22.23.4-r0 | BELL-CVE-2026-106069 |
| Alpaquita | 25, stream | nodejs24 | 24.22.1-r0 | BELL-CVE-2026-106069 |
| Alpaquita | stream | nodejs26 | 26.12.1-r1 | BELL-CVE-2026-106069 |
| BellSoft Hardened Containers | 25 | nodejs26 | 26.12.1-r0 | BELL-CVE-2026-106069 |
| BellSoft Hardened Containers | 25, stream | nodejs22 | 22.23.4-r0 | BELL-CVE-2026-106069 |
| BellSoft Hardened Containers | 25, stream | nodejs24 | 24.22.1-r0 | BELL-CVE-2026-106069 |
| BellSoft Hardened Containers | stream | nodejs26 | 26.12.1-r1 | BELL-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 rates this Important.
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.
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)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | nodejs24-1:24.22.1-3.el10_2 | Fixed 2026-11-09 | RHSA-2026:96088 |
| Red Hat Enterprise Linux 10 | nodejs22-1:22.23.4-1.el10_2 | Fixed 2026-11-09 | RHSA-2026:96094 |
| Red Hat Enterprise Linux 8 | nodejs:24-8100020261027151919.6d880403 | Fixed 2026-10-29 | RHSA-2026:92376 |
| Red Hat Enterprise Linux 8 | nodejs:22-8100020261104150431.6d880403 | Fixed 2026-11-11 | RHSA-2026:98113 |
| Red Hat Enterprise Linux 9 | nodejs:24-9080020261027142403.rhel9 | Fixed 2026-10-29 | RHSA-2026:92378 |
| Red Hat Enterprise Linux 9 | nodejs:22-9080020261103125134.rhel9 | Fixed 2026-11-09 | RHSA-2026:96234 |
| Red Hat Enterprise Linux 10 | nodejs26 | Affected | |
| Red Hat Enterprise Linux 9 | nodejs:26/nodejs | Affected | |
| Red Hat Hardened Images | hi/nodejs | Not affected | |
| Red Hat Hardened Images | nodejs20 | Not affected | |
| Red Hat Hardened Images | nodejs22 | Not affected | |
| Red Hat Hardened Images | nodejs24 | Not affected | |
| Red Hat Hardened Images | nodejs25 | Not affected | |
| Red Hat Hardened Images | nodejs26 | Not 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.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.