Loading vulnerability…
CVE-2026-44909 is a denial-of-service vulnerability in Proxygen caused by the absence of a generalized slow-consumer detection mechanism in the core HTTP session layer. In affected versions, a remote client can abuse HTTP/2 flow-control semantics by advertising SETTINGS_INITIAL_WINDOW_SIZE as zero or by withholding WINDOW_UPDATE frames, preventing the server from transmitting response data while still allowing request processing to continue. The vulnerable implementation continues generating complete response bodies and buffers them in memory for stalled streams instead of applying sufficient backpressure or terminating the connection. By opening many concurrent streams and requesting large resources, an unauthenticated attacker can force unbounded accumulation of buffered response data in memory. Affected versions are v2017.01.16.00 through v2026.07.20.00.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An HTTP/2 denial-of-service vulnerability involving abuse of flow-control behavior that can cause memory amplification and crash vulnerable servers through memory exhaustion.
A tracked CVE associated with the coordinated HTTP/2 flow-control denial-of-service issue affecting multiple server implementations; the specific affected product is not identified in the content.
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.