nodejs · Node.js · published 2026-06-26

CVE-2026-48619

Routine No exploitation evidence; EPSS 0.6%.

CVE-2026-48619 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 51% of all CVEs. This Node.js vulnerability: CVSS 5.3 (v3.0), attacks can be automated. Fixed upstream in Node.js 26.3.1, 24.17.0, 22.23.0. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Node.js 26.3.1, 24.17.0, 22.23.0.

Patch events

  1. This monthSecurity release

    Language runtimeNode.js

    Node.js security releases: 26.3.1, 24.17.0, 22.23.0

    Upgrade to 26.3.124.17.022.23.0

    Why: CVE-2026-48618: EPSS 3.1% with high severity (CVSS 7.7).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.6% (52th pct)FIRST EPSS v2026.06.15
CVSS base score5.3 (v3.0)
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

A flaw in Node.js HTTP/2 client allows a server to send an unlimited number of ORIGIN frames, which could lead to an Out of Memory error on the client. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

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 →