CVE-2026-53715 is a medium-severity (CVSS 5.3) CWE-362 vulnerability in github.com/envoyproxy/gateway. A fix is available for github.com/envoyproxy/gateway — see the affected versions and patch details below.
Envoy Gateway: Wasm cache ServeHTTP reads mappingPath2Cache without lock
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-53715.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-53715 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/envoyproxy/gateway🐹github.com/envoyproxy/gatewayReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Vulnerability report without repro case. Repro case may be added later after harness is complete.
Preconditions (4):
- Pod-network reachability to :18002 (no auth)
- Tenant can create EnvoyExtensionPolicy (baseline)
- Attacker pod floods GET while churning EnvoyExtensionPolicy with distinct Wasm URLs
- Read at :153 must overlap a write at :201/:209 (probabilistic, attacker controls both rates)
Description:
httpserver.go:153 reads s.mappingPath2Cache with no lock while httpserver.go:201/209 write it under s.Lock(); the struct uses a plain map. Writer is tenant-reachable via EnvoyExtensionPolicy translation, reader is pod-network-reachable on :18002 with per-request goroutines. Go's concurrent map read+write detection calls runtime.throw, which net/http's per-conn recover cannot catch, so the controller process exits — cross-tenant control-plane DoS. Capped at MEDIUM: DoS-only, k8s restarts pod, timing-dependent trigger.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/envoyproxy/gateway | ≥ 1.8.0-rc.0&&< 1.8.1 | 1.8.1go get github.com/envoyproxy/gateway@v1.8.1 |
| 🐹Go | github.com/envoyproxy/gateway | all versions | 1.7.4go get github.com/envoyproxy/gateway@v1.7.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/envoyproxy/gateway, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/envoyproxy/gateway to 1.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-53715 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat Connectivity Link includes an affected Envoy Gateway version below 1.7.4. An authorized tenant with pod-network access can trigger a timing-dependent controller crash by concurrently flooding the unauthenticated Wasm cache endpoint and churning policies with distinct Wasm URLs.
Restrict pod-network access to port 18002 and limit untrusted tenants' permission to create or modify EnvoyExtensionPolicy resources. These controls reduce exposure but do not eliminate the race for authorized users.Source: Red Hat security advisory for CVE-2026-53715 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-53715 in your dependencies?
Find it across Go, including transitive dependencies.