CVE-2026-53716: CWE-789: Memory Allocation with Excessive Size Value in envoyproxy gateway
Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, getFileFromGZ in internal/wasm/httpfetcher.go calls io.ReadAll on a gzip.Reader without limiting decompressed output when a tenant-controlled EnvoyExtensionPolicy.spec.wasm[].code.http.url points to a reachable compressed Wasm payload. The 256 MiB compressed-input cap does not constrain the expanded size, no operator Wasm URL allowlist exists, and the optional sha256 check occurs only after decompression, so a comparatively small gzip stream can force a multi-gigabyte allocation in the shared controller. The resulting out-of-memory termination restarts the controller, re-reconciles the persistent custom resource, and can create a persistent cross-tenant control-plane outage. This issue is fixed in versions 1.7.4 and 1.8.1.
AI Analysis
Technical Summary
Envoy Gateway versions before 1.7.4 and between 1.8.0-rc.0 and before 1.8.1 contain a memory allocation vulnerability (CWE-789) in the getFileFromGZ function within internal/wasm/httpfetcher.go. The function calls io.ReadAll on a gzip.Reader without limiting the decompressed output size, allowing a compressed Wasm payload controlled by a tenant to trigger multi-gigabyte memory allocations despite a 256 MiB compressed input cap. There is no operator Wasm URL allowlist, and the optional sha256 integrity check occurs only after decompression. This can cause the shared controller to run out of memory, terminate, and restart, leading to persistent cross-tenant control-plane outages. The vulnerability is addressed in Envoy Gateway versions 1.7.4 and 1.8.1.
Potential Impact
An attacker controlling the EnvoyExtensionPolicy.spec.wasm[].code.http.url can supply a compressed Wasm payload that decompresses to a very large size, causing the Envoy Gateway controller to allocate excessive memory and crash. This results in out-of-memory termination and restarts of the controller, which re-reconciles persistent custom resources, potentially causing persistent cross-tenant control-plane outages. There is no impact on confidentiality or integrity reported, but availability is severely affected.
Mitigation Recommendations
This vulnerability is fixed in Envoy Gateway versions 1.7.4 and 1.8.1. Users should upgrade to these versions or later to remediate the issue. No other mitigations such as URL allowlisting or decompression limits are indicated in the advisory. Patch status is confirmed by the vendor advisory.
CVE-2026-53716: CWE-789: Memory Allocation with Excessive Size Value in envoyproxy gateway
Description
Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, getFileFromGZ in internal/wasm/httpfetcher.go calls io.ReadAll on a gzip.Reader without limiting decompressed output when a tenant-controlled EnvoyExtensionPolicy.spec.wasm[].code.http.url points to a reachable compressed Wasm payload. The 256 MiB compressed-input cap does not constrain the expanded size, no operator Wasm URL allowlist exists, and the optional sha256 check occurs only after decompression, so a comparatively small gzip stream can force a multi-gigabyte allocation in the shared controller. The resulting out-of-memory termination restarts the controller, re-reconciles the persistent custom resource, and can create a persistent cross-tenant control-plane outage. This issue is fixed in versions 1.7.4 and 1.8.1.
CVSS v3.1
Score 6.5medium
Affected software
envoyproxy
gateway
pkg:github/envoyproxy/gatewayRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Envoy Gateway versions before 1.7.4 and between 1.8.0-rc.0 and before 1.8.1 contain a memory allocation vulnerability (CWE-789) in the getFileFromGZ function within internal/wasm/httpfetcher.go. The function calls io.ReadAll on a gzip.Reader without limiting the decompressed output size, allowing a compressed Wasm payload controlled by a tenant to trigger multi-gigabyte memory allocations despite a 256 MiB compressed input cap. There is no operator Wasm URL allowlist, and the optional sha256 integrity check occurs only after decompression. This can cause the shared controller to run out of memory, terminate, and restart, leading to persistent cross-tenant control-plane outages. The vulnerability is addressed in Envoy Gateway versions 1.7.4 and 1.8.1.
Potential Impact
An attacker controlling the EnvoyExtensionPolicy.spec.wasm[].code.http.url can supply a compressed Wasm payload that decompresses to a very large size, causing the Envoy Gateway controller to allocate excessive memory and crash. This results in out-of-memory termination and restarts of the controller, which re-reconciles persistent custom resources, potentially causing persistent cross-tenant control-plane outages. There is no impact on confidentiality or integrity reported, but availability is severely affected.
Mitigation Recommendations
This vulnerability is fixed in Envoy Gateway versions 1.7.4 and 1.8.1. Users should upgrade to these versions or later to remediate the issue. No other mitigations such as URL allowlisting or decompression limits are indicated in the advisory. Patch status is confirmed by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-10T16:43:31.241Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa85d5955bf5e2cf598a21f
Added to database: 09/14/2026, 20:47:21 UTC
Last enriched: 09/14/2026, 21:02:22 UTC
Last updated: 09/15/2026, 05:09:48 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.