All vulnerabilities

Servers and applications

CVE-2026-47774

HTTP/2 memory exhaustion via cookie header size bypass and HPACK amplification

Severity
High 7.5
Published
3 Jun 2026
Last changed
26 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
1.35.11, 1.36.7, 1.37.3
Exploit chance
1% in the next 30 daysHigher than 62% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
CWE-405Allocation without limits (CWE-770)Decompression bomb (CWE-409)
Attack
Over the network · No login needed · No user action needed
Attacker can
Take it down
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Also known as
GHSA-22m2-hvr2-xqc8
Sources
NVD, Project advisories (GitHub)

Description

A vulnerability in Envoy's HTTP/2 downstream request processing allows an unauthenticated remote client to trigger excessive memory consumption, potentially resulting in OOM termination of the Envoy process and denial of service.

The issue arises from the combination of two behaviors:

  • Cookie header bytes are not fully accounted for during request header size validation in Envoy.
  • HPACK header block limits in oghttp2/quiche are enforced on encoded bytes without a corresponding limit on total decoded header size.

Together, these behaviors allow a malicious client to cause large decoded header allocations while bypassing the intended request header size protections.

During HTTP/2 request processing, cookie header fragments are buffered separately and merged only after request header size validation has completed. Because these buffered cookie bytes are not fully included in the effective header size check, oversized cookie data can bypass max_request_headers_kb enforcement.

From envoyproxy/envoy's security advisory. Shortened; the full text is there.

Workarounds

No complete workaround is known short of applying a fix.

Possible temporary mitigations include:

  • disabling downstream HTTP/2 where operationally feasible;
  • enforcing stricter request header and cookie limits before traffic reaches Envoy; and
  • monitoring Envoy memory usage for abnormal growth under HTTP/2 traffic.
Workarounds as given by envoyproxy/envoy's security advisory.

Affected software

SoftwareAffected versions
EnvoyServers and applications · cpe:a:envoyproxy:envoy
  • Every version before 1.35.11
  • From 1.36.0 before 1.36.7
  • From 1.37.0 before 1.37.3
  • Version 1.38.0
EnvoyServers and applications · github:envoyproxy/envoy
  • Every version before 1.35.11

About Envoy

service proxy

From Wikidata, CC0 1.0.
Docker Hub pulls
5,809,928,938Docker Hub, 15 Nov 2026
GitHub stars
29,237GitHub, 15 Nov 2026
Forks
5,728GitHub, 15 Nov 2026
Latest release
v1.40.2GitHub, 15 Nov 2026
Released
27 Oct 2026GitHub
Developer
Alyssa WilkWikidata
License
Apache Software License 2.0Wikidata
Written in
C++Wikidata
First released
8 Aug 2016Wikidata
First published on GitHub
8 Aug 2016GitHub

Release lines

ReleaseLatestSecurity fixes
1.401.40.2Until 13 Oct 2027
1.391.39.6Until 14 Jul 2027
1.381.38.9Until 23 Apr 2027
1.371.37.11Until 13 Jan 2027
1.361.36.13Ended 14 Oct 2026
1.351.35.13Ended 23 Jul 2026

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-47774
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-47774
  • GitHub Advisory Database https://github.com/advisories/GHSA-22m2-hvr2-xqc8
  • github.com https://github.com/envoyproxy/envoy/security/advisories/GHSA-22m2-hvr2-xqc8