CyberRota Analysis
AI-GeneratedKubernetes environments using Envoy Gateway versions prior to 1.7.4 and 1.8.1 are vulnerable to a denial-of-service attack due to improper handling of decompressed output from tenant-controlled Wasm payloads. An attacker can exploit this flaw to trigger excessive memory allocation, leading to out-of-memory conditions that restart the controller and disrupt service across tenants. Organizations utilizing these versions should prioritize upgrading to the patched releases to mitigate the risk of control-plane outages.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD 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.