Loading vulnerability…
CVE-2026-59173 is an uncontrolled resource consumption vulnerability in Apache Traffic Server's handling of HTTP/2 flow-control under stalled transmission conditions. A remote client can abuse standard HTTP/2 mechanisms by advertising a zero or very small receive window, or by withholding WINDOW_UPDATE frames, causing the server to continue processing requests and generating full response bodies even though the client is not permitting the data to be sent. As a result, unsent response data accumulates in memory on a per-stream basis. By opening multiple streams and requesting large responses, an attacker can amplify memory usage and drive the server into resource exhaustion. Affected versions are Apache Traffic Server 9.0.0 through 9.1.13 and 10.0.0 through 10.1.2.
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.
8 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 denial-of-service vulnerability affecting Apache Traffic Server where mishandled HTTP/2 stalled flow control allows remote, unauthenticated attackers to trigger memory exhaustion by causing the server to buffer response data it cannot send.
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.