Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-53716— Envoy Gateway: Wasm HTTP fetch decompresses gzip without output-size limit

Quick assessment

Affected
envoyproxy gateway
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

以下是该漏洞描述信息的中文翻译： Envoy Gateway 是一个开源项目，用于将 Envoy Proxy 作为独立应用或基于 Kubernetes 的应用网关进行管理。在 1.7.4 和 1.8.1 版本之前， 中的 函数在对 gzip.Reader 调用 时，未对解压后的输出大小进行限制，而租户可通过 指定一个可访问的压缩 Wasm 载荷地址。 其中，256 MiB 的压缩输入上限并不能限制解压后的数据大小；系统中不存在操作员定义的 Wasm URL 白名单；且可选的 SHA-256 校验仅在解压之后才执行。

CVSS 6.5 · Medium EPSS 0.04% · P14
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-53716

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Envoy Gateway: Wasm HTTP fetch decompresses gzip without output-size limit
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
未经控制的内存分配
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
envoyproxy gateway < 1.7.4 -

II. Public POCs for CVE-2026-53716

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-53716

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-53716 (3)

Vendor Advisories for CVE-2026-53716 (1)

Vendor Pages for CVE-2026-53716 (2)

Same Patch Batch · envoyproxy · 2026-09-14 · 7 CVEs total

CVE-2026-53713 9.1 CRITICAL Envoy Gateway: Authentication Bypass via Improper Input Validation in EnvoyExtensionPolicy
CVE-2026-53714 7.4 HIGH Envoy Gateway: xDS Control Plane Information Disclosure when Envoy Gateway operates in Gat
CVE-2026-53719 6.5 MEDIUM Envoy Gateway: Nil-dereference when SecurityPolicy targets TCPRoute without spec.authoriza
CVE-2026-53717 6.5 MEDIUM Envoy Gateway: OCI layer extraction allocates make([]byte, h.Size) from untrusted tar head
CVE-2026-53718 6.4 MEDIUM Envoy Gateway custom backendRef cross-namespace ReferenceGrant bypass
CVE-2026-53715 5.3 MEDIUM Envoy Gateway: Wasm cache ServeHTTP reads mappingPath2Cache without lock

IV. Related Vulnerabilities

Same product: gateway
Same vendor: envoyproxy
Same weakness: CWE-789

V. Comments for CVE-2026-53716

No comments yet

Leave a comment