Skip to main content
Mallory
HighVulnerability

CVE-2026-44909: HTTP/2 flow-control slow-consumer DoS in Proxygen

Published Jul 23, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS0.57%48th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-44909CWE-400

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.

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.

Successful exploitation can cause unbounded memory growth on the server, resulting in resource exhaustion and denial of service. Depending on system limits and deployment characteristics, the outcome may include severe service degradation, exhaustion of worker or connection resources, swap thrashing, process termination due to out-of-memory conditions, or broader host instability that prevents legitimate users from accessing the service.

Mitigation

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

If immediate patching is not possible, reduce exposure by enforcing strict memory ceilings for buffered response data, limiting the number of concurrent HTTP/2 streams per connection, and aggressively terminating connections that exhibit stalled or abusive flow-control behavior. Additional defensive measures include tightening timeouts and ensuring backpressure mechanisms prevent indefinite buffering of unsent response bodies.

Remediation

Patch, then assume compromise.

Upgrade Proxygen to a release newer than v2026.07.20.00 that includes a fix for the missing slow-consumer detection and improved handling of stalled HTTP/2 flow-control conditions. Apply vendor-provided updates promptly across all deployments using affected Proxygen versions.

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.
FAQ

Frequently asked questions

Is CVE-2026-44909 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-44909 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-44909?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-44909.
Is there a patch for CVE-2026-44909?
Upgrade Proxygen to a release newer than v2026.07.20.00 that includes a fix for the missing slow-consumer detection and improved handling of stalled HTTP/2 flow-control conditions. Apply vendor-provided updates promptly across all deployments using affected Proxygen versions.
How severe is CVE-2026-44909?
CVE-2026-44909 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.57% (48th percentile) as of Sep 25, 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 activity3Community discussion across Reddit, Mastodon, and other social sources.