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

CVE-2026-105481

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-105481 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 25% of all CVEs. This Node.js vulnerability: CVSS 6.5 (v3.0). Fixed upstream in Node.js 26.12.1, 24.22.1, 22.23.4; Debian, Ubuntu and Red Hat Enterprise Linux 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 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. 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% (25th pct)FIRST EPSS v2026.06.15
CVSS base score6.5 (v3.0)
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request. This is an incomplete fix of CVE-2026-48931. The guard that destroys idle keep-alive sockets when unexpected data arrives only runs when the event loop polls for I/O. If an unsolicited response has already reached the socket but has not been read yet when the socket is handed to a new request, for example because the event loop was busy with synchronous work, the guard is removed without seeing it and the data is parsed as the response to the new request. 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 →