Loading vulnerability…
CVE-2026-56846 is a high-severity resource-exhaustion flaw in Node.js HTTP/2 handling. Retained HTTP/2 header blocks are not correctly accounted for against the configured maxSessionMemory limit, allowing them to bypass the session memory restriction. Specially crafted HTTP/2 traffic can consequently drive unbounded or excessive memory consumption in an affected Node.js process. The vulnerability affects Node.js 22.x and 24.x.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability addressed by the AlmaLinux 9 Node.js-related security update RHSA-2026:61386.
A vulnerability addressed by the Alma Linux ALSA-2026-61377 security update for Node.js 24 packages.
A vulnerability addressed by AlmaLinux advisory ALSA-2026:61376 affecting the listed Node.js packages on AlmaLinux 10. The content does not provide a vulnerability-specific technical description.
A Node.js HTTP/2 flaw that allows remote memory exhaustion through retained header blocks, resulting in denial of service.
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.