{"document":{"category":"csaf_vex","csaf_version":"2.0","title":"CVE-2026-47774: Envoy vulnerable to HTTP/2 memory exhaustion via cookie header size bypass and HPACK amplification","publisher":{"category":"vendor","name":"HarborGuard Database","namespace":"https://database.harborguard.co"},"tracking":{"id":"CVE-2026-47774","status":"final","version":"1","initial_release_date":"2026-06-17T16:58:36.541Z","current_release_date":"2026-06-17T18:01:59.116Z","revision_history":[{"date":"2026-06-17T16:58:36.541Z","number":"1","summary":"Initial machine-readable export from HarborGuard."}]},"distribution":{"tlp":{"label":"WHITE"},"text":"Public CVE data; freely redistributable."},"notes":[{"category":"description","text":"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.","title":"CVE description"}],"references":[{"category":"self","summary":"CVE-2026-47774 on HarborGuard Database","url":"https://database.harborguard.co/cve/CVE-2026-47774"},{"category":"external","summary":"CVE Record","url":"https://www.cve.org/CVERecord?id=CVE-2026-47774"},{"category":"external","summary":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-22m2-hvr2-xqc8","url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-22m2-hvr2-xqc8"}]},"product_tree":{"branches":[{"category":"vendor","name":"envoyproxy","branches":[{"category":"product_name","name":"envoy","branches":[{"category":"product_version","name":"< 1.35.11","product":{"name":"envoyproxy envoy < 1.35.11","product_id":"CSAFPID-1","product_identification_helper":{"cpe":"cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*"}}},{"category":"product_version","name":">= 1.36.0, < 1.36.7","product":{"name":"envoyproxy envoy >= 1.36.0, < 1.36.7","product_id":"CSAFPID-2","product_identification_helper":{"cpe":"cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*"}}},{"category":"product_version","name":">= 1.37.0, < 1.37.3","product":{"name":"envoyproxy envoy >= 1.37.0, < 1.37.3","product_id":"CSAFPID-3","product_identification_helper":{"cpe":"cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*"}}},{"category":"product_version","name":">= 1.38.0, < 1.38.1","product":{"name":"envoyproxy envoy >= 1.38.0, < 1.38.1","product_id":"CSAFPID-4","product_identification_helper":{"cpe":"cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*"}}}]}]}]},"vulnerabilities":[{"cve":"CVE-2026-47774","title":"Envoy vulnerable to HTTP/2 memory exhaustion via cookie header size bypass and HPACK amplification","notes":[{"category":"description","text":"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.","title":"CVE description"}],"product_status":{"known_affected":["CSAFPID-1","CSAFPID-2","CSAFPID-3","CSAFPID-4"]},"scores":[{"cvss_v3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH"},"products":["CSAFPID-1","CSAFPID-2","CSAFPID-3","CSAFPID-4"]}],"remediations":[{"category":"none_available","details":"No fixed version is published yet. Monitor the upstream advisory.","product_ids":["CSAFPID-1","CSAFPID-2","CSAFPID-3","CSAFPID-4"]}]}]}