CVE-2026-59173 is an important denial-of-service vulnerability in Apache Traffic Server affecting HTTP/2 handling under stalled flow-control conditions. A remote client can abuse standard HTTP/2 flow-control mechanisms by advertising an effectively unusable receive window, such as an initial window size of zero, or by withholding WINDOW_UPDATE frames after issuing requests. In vulnerable versions, Apache Traffic Server may continue processing requests and generating response bodies even when outbound transmission is blocked by the client-controlled flow-control state. This causes response data to be buffered per stalled stream, allowing an attacker to accumulate excessive server-side memory consumption across many concurrent streams and requests for large resources. Affected versions are Apache Traffic Server 9.0.0 through 9.2.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.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.