CVE-2026-53717

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 48% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
30(Track)
EG Risk 30/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

July 16, 2026

Last Modified

September 15, 2026

Advisory Details (9)

Auto-updated Sep 14, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

OCI layer extraction allocates make([]byte, h.Size) from untrusted tar header · Advisory · envoyproxy/gateway · GitHub

https://github.com/envoyproxy/gateway/security/advisories/GHSA-h7pq-86h8-rp5x
github_release Patch Available

v1.8.1

Patch available: envoyproxy/gateway v1.8.1

https://github.com/envoyproxy/gateway/releases/tag/v1.8.1
github_release Patch Available

v1.7.4

Patch available: envoyproxy/gateway v1.7.4

https://github.com/envoyproxy/gateway/releases/tag/v1.7.4
github_pr

fix github SA for June release

Fix merged in envoyproxy/gateway PR #9173 on 2026-06-05 — awaiting tagged release

https://github.com/envoyproxy/gateway/pull/9173
github_pr

[release-1.8] fix github SA for June release

Fix merged in envoyproxy/gateway PR #9172 on 2026-06-05 — awaiting tagged release

https://github.com/envoyproxy/gateway/pull/9172
github_pr

[release-1.7] fix github SA for June release

Fix merged in envoyproxy/gateway PR #9171 on 2026-06-05 — awaiting tagged release

https://github.com/envoyproxy/gateway/pull/9171
github_commit

commit b4737180c7e5 (envoyproxy/gateway)

Fix landed in envoyproxy/gateway commit b4737180c7e5 — awaiting tagged release

https://github.com/envoyproxy/gateway/commit/b4737180c7e597490c6363075c565fa8cf24eead
github_commit

commit 96e2b750868a (envoyproxy/gateway)

Fix landed in envoyproxy/gateway commit 96e2b750868a — awaiting tagged release

https://github.com/envoyproxy/gateway/commit/96e2b750868a459ace4b8b68e6a6e4fb0152b9b7
github_commit

commit 5a78db82b7cf (envoyproxy/gateway)

Fix landed in envoyproxy/gateway commit 5a78db82b7cf — awaiting tagged release

https://github.com/envoyproxy/gateway/commit/5a78db82b7cf4fc5bebbeda2c50952892038a464

Vendor Advisories for CVE-2026-53717(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/envoyproxy/gateway—1.8.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 10:48 UTCEG score recompute
  3. 2026-09-17 10:29 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 20:47 UTCEG score recompute
  7. 2026-09-15 19:41 UTCEG score recompute
  8. 2026-09-14 20:27 UTCEG score recompute
  9. 2026-07-30 12:30 UTCEG score recompute
  10. 2026-07-26 11:25 UTCEG score recompute
  11. 2026-07-23 03:19 UTCEG score recompute
  12. 2026-07-16 20:05 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53717?
CVE-2026-53717 is a medium vulnerability published on July 16, 2026. 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…
When was CVE-2026-53717 disclosed?
CVE-2026-53717 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53717 actively exploited?
CVE-2026-53717 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53717?
CVE-2026-53717 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-53717?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53717, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53717

Explore →

Is Your Infrastructure Affected by CVE-2026-53717?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs