Skip to main content
Mallory
← Back to News
widely-deployed-product-advisoryinternet-facing-service-vulnerabilityproof-of-concept-release

HTTP/2 Flow-Control Flaw Enables Unauthenticated Server Memory Exhaustion

Patch & Detection Intelligence · 2 sources · Updated 4mo ago · First seen Jul 23, 2026

HTTP/2 Flow-Control Flaw Enables Unauthenticated Server Memory Exhaustion

A newly disclosed denial-of-service flaw in multiple HTTP/2 server implementations allows remote, unauthenticated attackers to exhaust memory and crash services by abusing normal flow-control behavior. By stalling outbound data transmission—such as by manipulating SETTINGS_INITIAL_WINDOW_SIZE or withholding WINDOW_UPDATE frames—an attacker can cause vulnerable servers to keep generating and buffering full responses, leading to out-of-memory conditions, swap thrashing, worker-thread exhaustion, service freezes, or kernel OOM kills. CERT/CC is tracking the issue after it was reported by the Okta Red Team, and the coordinated disclosures include CVE-2026-44909, CVE-2026-59173, and CVE-2026-59762.

Affected vendors named in advisories include Apache Traffic Server, Citrix, F5 Networks, Meta, Red Hat, SUSE, and Yahoo. Apache Traffic Server users were advised to upgrade to versions 9.1.14 or 10.1.3, while F5 published guidance for BIG-IP and other vendors issued product-specific fixes or mitigations. Recommended defenses include stricter memory limits, limiting concurrent HTTP/2 streams, terminating stalled connections, and improving timeout and backpressure handling. No public exploitation has been confirmed, but the low complexity of the attack has prompted calls for rapid patching and configuration hardening.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Jul 23, 2026 – Jul 24, 2026
  1. Jul 24, 20264mo ago

    Okta Red Team reports HTTP/2 flow-control DoS vulnerability

    The HTTP/2 denial-of-service issue was reported by the Okta Red Team. The flaw involves abusing normal flow-control behavior so servers buffer unsent response data until memory is exhausted.

    New HTTP/2 Flaw Lets Unauthenticated Attackers Crash Servers With Memory Exhaustion Attacks
  2. Jul 23, 20264mo ago

    F5 and other vendors issue patches and mitigations

    Affected vendors including F5 began releasing fixes, advisories, and mitigations for the HTTP/2 memory-exhaustion flaw. Recommended defenses included stricter memory limits, limiting concurrent HTTP/2 streams, terminating stalled connections, and improving timeout and backpressure handling.

    HTTP/2 DoS Flaw Lets Attackers Exhaust Server Memory
  3. Jul 23, 20264mo ago

    Apache Traffic Server publishes fixes for affected versions

    Apache Traffic Server published fixes or advisories for its affected HTTP/2 implementation. Users were advised to upgrade to versions 9.1.14 or 10.1.3.

    HTTP/2 DoS Flaw Lets Attackers Exhaust Server Memory
  4. Jul 23, 20264mo ago

    CERT/CC tracks coordinated HTTP/2 DoS disclosures

    CERT/CC began tracking the coordinated disclosure covering multiple CVEs affecting HTTP/2 implementations, including CVE-2026-44909, CVE-2026-59173, and CVE-2026-59762. The issue affects multiple vendors and can lead to freezes, crashes, or out-of-memory conditions.

    HTTP/2 DoS Flaw Lets Attackers Exhaust Server Memory
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

3 linked
Big-IpApache Traffic ServerTraffic Server

Organizations

7 linked
Red HatApache Software FoundationSuseMeta PlatformsF5Citrix SystemsYahoo
Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.