CVE-2026-53717
Fixed in a distro release EPSS <1%CVSS 6.5
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.
Products: envoyproxy gateway
Fixed upstream
| Ecosystem | Package | Fixed in |
|---|---|---|
| Go | github.com/envoyproxy/gateway | 1.8.1 |
| Go | github.com/envoyproxy/gateway | 1.7.4 |
Distro releases
| Release | Package | Fixed in |
|---|---|---|
| Chainguard | datadog-agent-7.76 | no fix |
| Chainguard | datadog-cluster-agent-7.73 | 7.73.3-r23 |
| Chainguard | datadog-cluster-agent-7.74 | 7.74.1-r24 |
| Chainguard | datadog-cluster-agent-7.75 | no fix |
| Chainguard | datadog-cluster-agent-7.76 | 7.76.3-r32 |
| Chainguard | datadog-cluster-agent-7.77 | 7.77.3-r23 |
| Chainguard | datadog-cluster-agent-7.78 | 7.78.4-r16 |
| Chainguard | datadog-cluster-agent-7.79 | 7.79.2-r15 |
| Chainguard | datadog-cluster-agent-7.80 | 7.80.4-r7 |
| Chainguard | datadog-cluster-agent-fips-7.73 | 7.73.3-r26 |
| Chainguard | datadog-cluster-agent-fips-7.74 | 7.74.1-r26 |
| Chainguard | datadog-cluster-agent-fips-7.75 | no fix |
| Chainguard | datadog-cluster-agent-fips-7.76 | 7.76.3-r32 |
| Chainguard | datadog-cluster-agent-fips-7.77 | 7.77.3-r29 |
| Chainguard | datadog-cluster-agent-fips-7.78 | 7.78.4-r14 |
| Chainguard | datadog-cluster-agent-fips-7.79 | 7.79.2-r8 |
| Chainguard | datadog-cluster-agent-fips-7.80 | 7.80.4-r5 |
| Chainguard | envoy-gateway-1.5 | no fix |
| Chainguard | envoy-gateway-1.5-egctl | no fix |
| Chainguard | envoy-gateway-1.6 | no fix |
| Chainguard | envoy-gateway-1.6-egctl | no fix |
| Chainguard | envoy-gateway-fips-1.5 | no fix |
| Chainguard | envoy-gateway-fips-1.5-egctl | no fix |
| Chainguard | envoy-gateway-fips-1.6 | no fix |
| Chainguard | envoy-gateway-fips-1.6-egctl | no fix |
| Chainguard | gitlab-operator | 3.1.2-r1 |
| Chainguard | gitlab-operator-fips | 3.2.0-r0 |
| Chainguard | tigera-operator-1.37 | no fix |
| Chainguard | tigera-operator-1.38 | 0 |
| Chainguard | tigera-operator-1.40 | 1.40.13-r4 |
| Chainguard | tigera-operator-1.41 | 0 |
| Chainguard | tigera-operator-1.42 | 1.42.4-r2 |
| Chainguard | tigera-operator-fips-1.37 | no fix |
| Chainguard | tigera-operator-fips-1.38 | 0 |
| Chainguard | tigera-operator-fips-1.40 | 1.40.13-r5 |
| Chainguard | tigera-operator-fips-1.41 | 0 |
| Chainguard | tigera-operator-fips-1.42 | 1.42.4-r4 |
| Wolfi | datadog-agent-7.76 | no fix |
| Wolfi | datadog-cluster-agent-7.73 | 7.73.3-r23 |
| Wolfi | datadog-cluster-agent-7.75 | no fix |
| Wolfi | datadog-cluster-agent-7.76 | 7.76.3-r32 |
| Wolfi | datadog-cluster-agent-7.77 | 7.77.3-r23 |
| Wolfi | datadog-cluster-agent-7.78 | 7.78.4-r16 |
| Wolfi | datadog-cluster-agent-7.79 | 7.79.2-r15 |
| Wolfi | datadog-cluster-agent-7.80 | 7.80.4-r7 |
| Wolfi | tigera-operator-1.40 | 1.40.13-r4 |
| Wolfi | tigera-operator-1.41 | 0 |
| Wolfi | tigera-operator-1.42 | 1.42.4-r2 |
| openSUSE Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 |