Node.js HTTP/2 client unbounded memory growth via ORIGIN frames
CVE-2026-48619 is a medium-severity vulnerability in the Node.js HTTP/2 client implementation (node:http2). A malicious or attacker-controlled HTTP/2 server can send an unlimited number of ORIGIN frames to a connecting Node.js HTTP/2 client. The client does not adequately bound memory consumption while processing and retaining attacker-controlled ORIGIN frame data, resulting in unbounded memory growth. This can ultimately trigger an out-of-memory condition and crash the client process.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity Node.js HTTP/2 vulnerability that can cause unbounded memory growth and resource exhaustion via attacker-controlled ORIGIN frames.
A medium-severity Node.js HTTP/2 client flaw that allows unbounded memory growth and can cause out-of-memory crashes.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.