Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-47774: Envoy HTTP/2 Memory Exhaustion via Cookie Header Bypass and HPACK Amplification

Published Jun 17, 2026 · Updated 15 days 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.97%63rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
Envoy ProxyRed Hat
IdentifiersCVE-2026-47774CWE-405 · Asymmetric Resource Consumption…

CVE-2026-47774 is a high-severity denial-of-service vulnerability in Envoy's downstream HTTP/2 request processing. Cookie fragments are buffered separately and are not fully included in request header size validation before merging, allowing decoded cookie data to bypass intended header limits. Concurrently, oghttp2/quiche limits HPACK encoded header blocks without enforcing a corresponding total decoded header size limit. Repeated compact HPACK dynamic-table references can therefore produce disproportionately large cookie allocations. HTTP/2 flow-control stalling can prolong allocation lifetimes and intensify memory exhaustion. An unauthenticated remote client can exploit these behaviors to exhaust memory and potentially cause out-of-memory termination. Fixed releases include Envoy 1.35.11, 1.36.7, 1.37.3, and 1.38.1.

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 exhaust Envoy process or container memory, cause OOM termination, and interrupt traffic handled by the affected proxy. Testing demonstrated approximately 32 GB of memory consumption in roughly 10 seconds from a single client using a 100 Mbps connection, with an estimated 5,700:1 wire-to-memory amplification ratio. Oversized decoded cookies forwarded upstream can also exceed upstream header limits, causing HTTP/2 connection resets and transient request failures. The vulnerability is rated CVSS v3.1 7.5, with high availability impact and no identified confidentiality or integrity impact.

Mitigation

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

No complete workaround is known other than applying the fix. Temporarily disable downstream HTTP/2 where operationally feasible, or enforce strict decoded request-header and cookie limits at a trusted component before traffic reaches Envoy. Monitor Envoy resident memory, OOM terminations, and unusual HTTP/2 traffic involving repeated indexed cookie references. Monitoring supports detection but does not prevent exploitation.

Remediation

Patch, then assume compromise.

Upgrade Envoy to 1.35.11, 1.36.7, 1.37.3, or 1.38.1, or a later release containing the fix. The patch includes buffered cookie bytes and fragment counts in HTTP/2 header-limit checks and enables decoded header-list size enforcement in oghttp2/quiche. Keep the default-enabled envoy.reloadable_features.http2_include_cookies_in_limits runtime feature enabled. Initial fixes introduced compatibility issues for legitimate cookie-heavy requests; use a current vendor-supported patched release that incorporates subsequent compatibility corrections and validate affected traffic during rollout. For bundled Envoy deployments, apply the corresponding vendor product update.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-49975Repository contains a Python proof-of-concept exploit for an HTTP/2 denial-of-service issue described as CVE-2026-49975, plus a companion defense-probing script and a local HTTP/2 test server. The main exploit file is http2_bomb.py, which manually builds HTTP/2 traffic using hyperframe and hpack rather than a higher-level HTTP client. It opens a TCP/TLS connection to a user-supplied host and port, negotiates ALPN 'h2' when TLS is enabled, sends the HTTP/2 connection preface and SETTINGS, and then performs the attack by abusing HPACK compression and HTTP/2 flow control. The exploit’s core capability is to insert small headers into the HPACK dynamic table and then send many indexed references across multiple streams, creating asymmetric server-side memory/bookkeeping cost. It also sets INITIAL_WINDOW_SIZE to 0 to inhibit response delivery and can periodically send WINDOW_UPDATE frames to keep the connection alive, effectively pinning allocations. Optional cookie fragmentation is included to try to bypass header-count limits. probe_defense.py is not the exploit itself; it is a detection/probing utility that connects to a target HTTP/2 service and evaluates whether mitigations appear present based on protocol behavior. test_server.py is a local vulnerable-style HTTP/2 server used for validation and demonstration; it listens with TLS, accepts HTTP/2 connections, decodes headers, and logs large header counts to simulate the vulnerable processing path. Repository structure is small and focused: 3 Python code files, 1 README, 1 requirements file, and .gitignore. Dependencies are h2/hpack/hyperframe. This is a real exploit repository, not just documentation, and its practical outcome is application-layer remote DoS rather than code execution. No hardcoded victim infrastructure is embedded; the operator supplies the target host and port at runtime.LiaoZiqi-GZFLS · Disclosed Jun 10, 2026 · python · markdown · networkOperational
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
Envoy ProxyEnvoyapplication
Red HatOpenshift Service Meshapplication
FAQ

Frequently asked questions

Is CVE-2026-47774 exploited in the wild?
As of Nov 7, 2026, Mallory has no reports of CVE-2026-47774 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-47774?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-47774, the earliest disclosed Jun 10, 2026.
Is there a patch for CVE-2026-47774?
Upgrade Envoy to 1.35.11, 1.36.7, 1.37.3, or 1.38.1, or a later release containing the fix. The patch includes buffered cookie bytes and fragment counts in HTTP/2 header-limit checks and enables decoded header-list size enforcement in oghttp2/quiche.
What products are affected by CVE-2026-47774?
Envoy Proxy Envoy and Red Hat Openshift Service Mesh.
How severe is CVE-2026-47774?
CVE-2026-47774 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.97% (63rd percentile) as of Nov 7, 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 activity9Community discussion across Reddit, Mastodon, and other social sources.