envoyproxy · Envoy · published 2026-06-17

CVE-2026-47774Envoy vulnerable to HTTP/2 memory exhaustion via cookie header size bypass and HPACK amplification

Routine No exploitation evidence; EPSS 1.0%.

CVE-2026-47774 is not known to be exploited in the wild. EPSS estimates a 1.0% chance of exploitation in the next 30 days, higher than 62% of all CVEs. This Envoy vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in Envoy 1.38.1, 1.37.3, 1.36.7, 1.35.11. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Envoy 1.38.1, 1.37.3, 1.36.7, 1.35.11.

Patch events

  1. This monthSecurity release

    Web serverEnvoy

    Envoy security releases: 1.38.1, 1.37.3, 1.36.7, 1.35.11

    Upgrade to 1.38.11.37.31.36.71.35.11

    Why: Vendor security release for server software (most severe: CVE-2026-47774).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)1.0% (63th pct)FIRST EPSS v2026.06.15
CVSS base score7.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to versions 1.35.11, 1.36.7, 1.37.3, and 1.38.1, 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. First, cookie header bytes are not fully accounted for during request header size validation in Envoy. Second, 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. Versions 1.35.11, 1.36.7, 1.37.3, and 1.38.1 contain a fix. 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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →