Loading vulnerability…
CVE-2026-56848 is a high-severity vulnerability in Node.js HTTP/2 handling that affects all active release lines at the time of disclosure. The flaw arises from a heap use-after-free condition triggered when the underlying nghttp2 library processes data while additional data is received concurrently. Under these conditions, memory that has already been freed can be referenced again during HTTP/2 processing, leading to memory corruption and process instability. The issue is reachable through HTTP/2 traffic handling in affected Node.js releases and can be triggered remotely by crafted protocol interactions.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.