nodejs · Node.js · published 2026-10-23

CVE-2026-106069

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-106069 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 23% of all CVEs. This Node.js vulnerability: CVSS 7.4 (v3.0), a successful attack gives total control of the component. Fixed upstream in Node.js 26.12.1, 24.22.1, 22.23.4; patched packages are out for Red Hat Enterprise Linux; Debian and Ubuntu still have unfixed releases. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Node.js 26.12.1, 24.22.1, 22.23.4.

Linux distribution packages

If you run the distro’s package rather than an upstream build, this is the version to look for.

DistroReleasePackageStatus
Debian13 trixienodejsNo fix yet
12 bookwormnodejsNo fix yet
Ubuntu26.04 LTSnodejsNo fix yet
24.04 LTSnodejsNo fix yet
Red Hat Enterprise LinuxRHEL 10nodejs22Fixed in 22.23.4-1.el10_2 RHSA-2026:96094
RHEL 10nodejs24Fixed in 24.22.1-3.el10_2 RHSA-2026:96088
RHEL 10nodejs26Fixed in 26.12.1-3.el10_3 RHSA-2026:98619

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Patch events

  1. Patch todaySecurity release

    Language runtimeNode.js

    Node.js security releases: 26.12.1, 24.22.1, 22.23.4

    Upgrade to 26.12.124.22.122.23.4

    Why: CVE-2026-111497: Known exploited server software, total technical impact.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (24th pct)FIRST EPSS v2026.06.15
CVSS base score7.4 (v3.0)
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →