CVE-2026-53717

Medium

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, internal/wasm/imagefetcher.go follows tenant-controlled EnvoyExtensionPolicy spec.wasm[].code.image.url values to Docker or OCI Wasm layers, and extractWasmPluginBinary uses the untrusted tar-header h.Size value to allocate memory before validating the entry name or declared size. A small PAX or GNU tar header can therefore claim a multi-terabyte entry even though the surrounding LimitReader restricts only the bytes read from the stream, and no registry allowlist prevents a permitted tenant from selecting an attacker-controlled registry that the controller can reach. The allocation is attempted for every tar entry and can cause an unrecoverable Go runtime out-of-memory failure; because the custom resource persists, reconciliation repeatedly crash-loops the shared controller and causes a single-request, non-volumetric, cluster-wide control-plane denial of service. This issue is fixed in versions 1.7.4 and 1.8.1.

SeverityMedium
CVSS6.5
Exploit probability—
ProductGithub.com/envoyproxy/gateway
PublishedSep 14, 2026
First seenSep 14, 2026
Weakness typeCWE-789CWE-789

How to fix

Update
  • github.com/envoyproxy/gateway1.8.1, 1.7.4 or later

Affected products

ProductAffected versionsFixed in
github.com/envoyproxy/gatewayGo1.8.0-rc.0 ≤ v < 1.8.1, v < 1.7.41.8.1, 1.7.4

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.