Skip to main content
Mallory
HighVulnerability

CVE-2026-59173: HTTP/2 Stalled Flow-Control Denial of Service in Apache Traffic Server

Published Jul 18, 2026 · Updated 23 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS7.5High · v3.1
EPSS0.74%56th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Apache Software Foundation
IdentifiersCVE-2026-59173CWE-400 · Uncontrolled Resource Consumption

CVE-2026-59173 is an uncontrolled resource consumption vulnerability in Apache Traffic Server's HTTP/2 handling. A remote, unauthenticated client can stall outbound flow control by advertising a zero initial window size or withholding WINDOW_UPDATE frames. Vulnerable servers continue processing requests and generating response bodies, retaining unsent data in memory until connections close or time out. Concurrent stalled streams requesting large responses amplify memory consumption and can cause denial of service. Affected releases include 10.0.0 through 10.1.2; the reported upper boundary for affected 9.x releases is inconsistent between 9.1.13 and 9.2.13.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation can exhaust server memory, degrade availability, freeze services, or cause process termination. Severe resource exhaustion can trigger kernel out-of-memory kills, swap thrashing, and system instability or crashes. Worker or connection exhaustion can also prevent legitimate clients from accessing services.

Mitigation

If you can’t patch tonight, do this now.

Enforce memory ceilings for buffered response data, restrict concurrent HTTP/2 streams per connection, and terminate connections exhibiting stalled flow control. Apply appropriate timeouts and backpressure so response generation cannot accumulate unbounded data while transmission is blocked.

Remediation

Patch, then assume compromise.

Upgrade Apache Traffic Server 10.x to 10.1.3 or a later fixed release. The supplied remediation information conflicts for 9.x: the vulnerability description identifies 9.1.14 as fixed, while an Apache advisory excerpt identifies 9.2.14 or later and extends the affected range through 9.2.13. Confirm the applicable fixed 9.x release against the current Apache advisory before deployment.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationTraffic Serverapplication
FAQ

Frequently asked questions

Is CVE-2026-59173 exploited in the wild?
As of Oct 29, 2026, Mallory has no reports of CVE-2026-59173 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-59173?
As of Oct 29, 2026, Mallory has found no public exploit for CVE-2026-59173.
Is there a patch for CVE-2026-59173?
Upgrade Apache Traffic Server 10.x to 10.1.3 or a later fixed release. The supplied remediation information conflicts for 9.x: the vulnerability description identifies 9.1.14 as fixed, while an Apache advisory excerpt identifies 9.2.14 or later and extends the affected range through 9.2.13.
What products are affected by CVE-2026-59173?
Apache Software Foundation Traffic Server.
How severe is CVE-2026-59173?
CVE-2026-59173 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.74% (56th percentile) as of Oct 29, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.