github.com/envoyproxy/gateway
Affected
- introduced
1.8.0-rc.0, fixed1.8.1(semver)
Fixed versions
1.8.1
Fix
- Fixed version
1.8.1go get github.com/envoyproxy/[email protected]
Advisory
Also known as: BIT-envoy-gateway-2026-53716, CVE-2026-53716, GO-2026-6006
Envoy Gateway: Wasm HTTP fetch decompresses gzip without output-size limit
Vulnerability report without repro case. Repro case may be added later after harness is complete.
Preconditions (4):
Description
getFileFromGZ calls io.ReadAll on a raw gzip.Reader (httpfetcher.go:216) with no output bound, while the compressed input is capped at 256 MiB (httpfetcher.go:139). The bytes originate from a tenant-controlled EnvoyExtensionPolicy.spec.wasm[].code.http.url (envoyextensionpolicy.go:1077 → cache.go:248 → httpfetcher.go:147 → :233), so an untrusted tenant can point at a ~10 MiB gzip-of-zeros and force ~10 GiB allocation in the shared controller process. All candidate guards execute either before the body is buffered or after decompression. OOM-kills, restarts, re-reconciles same CR, crash-loops — persistent cross-tenant control-plane outage with PR:L/AC:L and scope change → HIGH despite availability-only.
Medium Basis: The source's own band: MODERATE
1.8.0-rc.0, fixed 1.8.1 (semver)1.8.1
1.8.1go get github.com/envoyproxy/[email protected]0, fixed 1.7.4 (semver)1.7.4
1.7.4go get github.com/envoyproxy/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0