CVE-2026-53717
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Moderate risk: more likely to be exploited than 52% of all known CVEs.
References
Related Vulnerabilities
Other CWE-789 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-30522 | High | 7.5 | 90% | - | Fix |
| CVE-2026-49975 | High | 7.5 | 34% | - | Fix |
| CVE-2025-27533 | High | 7.5 | 8.7% | - | Fix |
| CVE-2017-7651 | High | 7.5 | 5.2% | - | Fix |
| CVE-2021-31811 | Medium | 5.5 | 3.4% | - | - |
| CVE-2021-27906 | Medium | 5.5 | 3.3% | - | Fix |
Common questions
How do I fix CVE-2026-53717?
No published fix for CVE-2026-53717 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-53717 being actively exploited?
Not that we know of. CVE-2026-53717 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.71% is the estimated probability that it will be exploited in the next 30 days. That is higher than 52% of all scored CVEs.
How severe is CVE-2026-53717?
CVE-2026-53717 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-53717
Markdown
[](https://tridentstack.com/cve/CVE-2026-53717)HTML
<a href="https://tridentstack.com/cve/CVE-2026-53717"><img src="https://tridentstack.com/cve/badge/CVE-2026-53717.svg" alt="CVE-2026-53717"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-15.