CVE-2026-53717

描述

Vulnerability report without repro case. Repro case may be added later after harness is complete. **Preconditions (4):** - Tenant can create EnvoyExtensionPolicy (baseline) - Controller has egress to attacker-controlled OCI registry - No registry allowlist (none exists in code) - Layer presents Docker/OCI media type **Description** At imagefetcher.go:287, make([]byte, h.Size) uses the attacker-controlled tar-header size; the LimitReader at :278 bounds bytes read from the stream but not the header-declared size returned by tr.Next() (a 512-byte header can claim a multi-TB entry via PAX/GNU encoding). Reached from untrusted tenant input via EnvoyExtensionPolicy spec.wasm[].code.image.url (envoyextensionpolicy.go:1157 → cache.go:262/299 → imagefetcher.go:218 → :287), and the allocation happens for every tar entry regardless of filename. The resulting Go runtime OOM throw is unrecoverable and, because the CRD persists, crash-loops the shared controller — single-request, non-volumetric, cluster-wide DoS.

如何修補 CVE-2026-53717

要修補 CVE-2026-53717,請將受影響套件升級到下列已修補版本。

• —升級至 1.8.1 或更新版本
• —升級至 1.7.4 或更新版本

CVE-2026-53717 正在被利用嗎?

目前沒有被利用訊號。CVE-2026-53717 既不在 CISA KEV 也沒有最新的 EPSS 分數。

受影響套件(2)

• >= 1.8.0-rc.0, < 1.8.1
• from 0, < 1.7.4, >= 1.8.0-rc.0, < 1.8.1

CVSS 分數

參考連結(2)

• PATCHgithub.com/envoyproxy/gateway
• WEBgithub.com/envoyproxy/gateway/security/advisories/GHSA-h7pq-86h8-rp5x