nodejs · Node.js · published 2026-11-11

CVE-2026-123872Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change

Routine No exploitation evidence; EPSS 0.4%.

CVE-2026-123872 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 36% of all CVEs. This Node.js vulnerability: CVSS 8.1 (v3.0), a successful attack gives total control of the component. Fixed upstream in Node.js 26.13.1, 24.22.3, 22.23.5; Debian, Ubuntu and Red Hat Enterprise Linux still have unfixed releases. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Node.js 26.13.1, 24.22.3, 22.23.5.

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 Linux (+3 more packages)RHEL 9nodejsNo fix yet
RHEL 8nodejsNo fix yet

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. This monthSecurity release

    Language runtimeNode.js

    Node.js security releases: 26.13.1, 24.22.3, 22.23.5

    Upgrade to 26.13.124.22.322.23.5

    Why: Vendor security release for server software (most severe: CVE-2026-123863).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (36th pct)FIRST EPSS v2026.06.15
CVSS base score8.1 (v3.0)
CVSS:3.0/AV:N/AC:L/PR:L/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 client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not authorized for. On a server that applies different client-certificate policies per hostname, for example stricter admin-only client-cert auth on one host and ordinary client-cert auth on another, a client that authenticates for a permitted host can renegotiate the TLS 1.2 connection under a different servername and carry its existing authentication to the protected host, bypassing the stricter policy. 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 →