CVE-2026-48619 — node
MEDIUMCVE-2026-48619 is a medium-severity (CVSS 5.3) Uncontrolled Resource Consumption vulnerability. No vendor fix is recorded yet; mitigation options are listed below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-48619.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-48619 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Description
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.
Affected Products
node.jsnodejsDetection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2026-48619 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This Moderate flaw in the Node.js HTTP/2 client can lead to a denial of service. A malicious server could exploit this by sending an excessive number of ORIGIN frames, causing the client to consume all available memory. This affects Red Hat products utilizing Node.js as an HTTP/2 client.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2026-48619 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | nodejs24-1:24.18.0-1.el10_2 | RHSA-2026:35841 |
| Red Hat Enterprise Linux 10 | nodejs22-1:22.23.1-2.el10_2 | RHSA-2026:35842 |
| Red Hat Enterprise Linux 8 | nodejs:24-8100020260630152626.6d880403 | RHSA-2026:39868 |
| Red Hat Enterprise Linux 8 | nodejs:22-8100020260703140402.6d880403 | RHSA-2026:41947 |
| Red Hat Enterprise Linux 9 | nodejs:24-9080020260626074955.rhel9 | RHSA-2026:35891 |
| Red Hat Enterprise Linux 9 | nodejs:22-9080020260626075442.rhel9 | RHSA-2026:35892 |
| Red Hat Hardened Images | nodejs26-main-11.17.0-1.26.4.0.1.3.hum1 | RHSA-2026:33866 |
| Red Hat Hardened Images | nodejs24-main-11.16.0-1.24.18.0.0.2.hum1 | RHSA-2026:34478 |
Frequently Asked Questions
Is CVE-2026-48619 in your dependencies?
Find it across , including transitive dependencies.