cve.bz

CVE-2026-106072 nodejs node: Improper Certificate Validation

6.7 mediumEPSS 0.6%

Medium (6.7) in nodejs node. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`. `tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

Severity

CVSS 3.0

6.7 medium
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
EPSS
0.6% (unchanged from 0.6% a week ago) estimated probability of exploitation activity in the next 30 days; 50th 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-106072 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106072?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106072?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-106072 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-106072
Debian14nodejs24.22.1+dfsg+~cs24.19.2-1DEBIAN-CVE-2026-106072
Ubuntu24.04:LTS, 26.04:LTS, 26.10 and 5 morenodejsno fix listedUBUNTU-CVE-2026-106072
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
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-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
AlmaLinux9npm1:11.19.1-1.24.22.1.3.module_el9.8.0+333+788f3075ALSA-2026:92378
AlmaLinux9v8-13.6-devel3:13.6.233.17-1.24.22.1.3.module_el9.8.0+333+788f3075ALSA-2026:92378
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-3.module+el9.8.0+40281+14cc6568RLSA-2026:92378
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40052+e32ea525RLSA-2026:92378
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40153+4d595597RLSA-2026:92378
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40165+d075e3f2RLSA-2026:92378
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.8.0+40164+8921ab53RLSA-2026:92378
Alpinev3.21, v3.22nodejs22.23.4-r0ALPINE-CVE-2026-106072
Alpinev3.23, v3.24nodejs24.22.1-r0ALPINE-CVE-2026-106072
Alpinev3.24nodejs-current26.12.1-r0ALPINE-CVE-2026-106072
Azure Linux3nodejs24.22.1-0AZL-111053
Alpaquita25nodejs2626.12.1-r0BELL-CVE-2026-106072
Alpaquita25, streamnodejs2222.23.4-r0BELL-CVE-2026-106072
Alpaquita25, streamnodejs2424.22.1-r0BELL-CVE-2026-106072
Alpaquitastreamnodejs2626.12.1-r1BELL-CVE-2026-106072
BellSoft Hardened Containers25nodejs2626.12.1-r0BELL-CVE-2026-106072
BellSoft Hardened Containers25, streamnodejs2222.23.4-r0BELL-CVE-2026-106072
BellSoft Hardened Containers25, streamnodejs2424.22.1-r0BELL-CVE-2026-106072
BellSoft Hardened Containersstreamnodejs2626.12.1-r1BELL-CVE-2026-106072

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

Red Hat's statement

This is a Moderate severity flaw, matching the upstream Node.js Medium rating. Red Hat aligns with the CNA CVSS (6.7): exploitation requires both a non-canonical IPv4 host form and a certificate with a DNS SAN for the canonical IP string that is already trusted by the client (Privileges Required: High relative to a generic network attacker without such a cert). On Red Hat platforms using glibc, the resolver accepts these spellings, so that part of the prerequisite is met. Successful abuse can confuse TLS endpoint identity with high confidentiality and integrity impact for the affected connection, but the trusted-cert barrier keeps the overall rating Moderate rather than Important.

Red Hat's mitigation

Use only canonical IPv4 literals or DNS names in Node.js TLS client connect targets; reject octal, hex, dword, and shortened IPv4 spellings in application input.

Where feasible, pin expected server certificates or public keys for sensitive outbound TLS.

Restrict which destinations Node.js workloads may reach with egress controls.

ProductPackageStateAdvisory
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 Enterprise Linux 10nodejs22Fix deferred
Red Hat Enterprise Linux 10nodejs24Fix deferred
Red Hat Enterprise Linux 10nodejs26Fix deferred
Red Hat Enterprise Linux 8nodejs:22/nodejsFix deferred
Red Hat Enterprise Linux 9nodejs:22/nodejsFix deferred
Red Hat Enterprise Linux 9nodejs:26/nodejsFix deferred
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-106072.

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