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

CVE-2026-123877Node.js is vulnerable to a certificate validation bypass in https.Agent via cross-policy TLS session reuse

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-123877 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 15% of all CVEs. This Node.js vulnerability: CVSS 6.8 (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.2% (16th pct)FIRST EPSS v2026.06.15
CVSS base score6.8 (v3.0)
CVSS:3.0/AV:N/AC:H/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 certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. 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 →