CVE-2026-53715: envoyproxy gateway · Race Condition
Affects envoyproxy gatewaySource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.8.1 or 1.7.4 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.8.1, 1.7.4
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade gateway and envoyproxy/gateway to 1.8.1 or 1.7.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| envoyproxygateway | Affected
| Fixed in
|
| envoyproxygateway | Affected
| Fixed in
|
GitHubenvoyproxy/gatewaypkg:github/envoyproxy/gatewayOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Envoy Gateway versions 1.7.4 and 1.8.1. Users should upgrade to these versions or later to remediate the issue. No additional mitigation actions are indicated by the vendor advisory.
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, HTTPServer.ServeHTTP in internal/wasm/httpserver.go reads the plain mappingPath2Cache map without synchronization while HTTPServer.Get writes the same map during EnvoyExtensionPolicy translation. An attacker with pod-network access to unauthenticated port 18002 and tenant permission to churn policies with distinct Wasm URLs can flood GET requests until a per-request reader overlaps a writer. Go's concurrent map read and write detection invokes runtime.throw, which the net/http connection recovery cannot catch, terminating the controller process and causing a timing-dependent, cross-tenant control-plane denial of service until Kubernetes restarts the pod. This issue is fixed in versions 1.7.4 and 1.8.1.
References
- github.com/envoyproxy/gateway/security/advisories/GHSA-8fv2-88gg-hm7q (opens in a new tab)
- github.com/envoyproxy/gateway/pull/9171 (opens in a new tab)
- github.com/envoyproxy/gateway/pull/9172 (opens in a new tab)
- github.com/envoyproxy/gateway/pull/9173 (opens in a new tab)
- github.com/envoyproxy/gateway/commit/5a78db82b7cf4fc5bebbeda2c50952892038a464 (opens in a new tab)
- github.com/envoyproxy/gateway/commit/96e2b750868a459ace4b8b68e6a6e4fb0152b9b7 (opens in a new tab)
- github.com/envoyproxy/gateway/commit/b4737180c7e597490c6363075c565fa8cf24eead (opens in a new tab)
- github.com/envoyproxy/gateway/releases/tag/v1.7.4 (opens in a new tab)
- github.com/envoyproxy/gateway/releases/tag/v1.8.1 (opens in a new tab)