Answer in brief
CVE-2026-53715 records a Medium severity (CVSS 5.3) vulnerability in Envoy Gateway: Wasm cache ServeHTTP reads mappingPath2Cache without lock. The current sources do not mark it as known exploited. The current feed maps envoyproxy/gateway (generic), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps envoyproxy/gateway (generic), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go), github.com/envoyproxy/gateway (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| envoyproxy/gatewaygeneric | <1.7.4 || >=1.8.0-rc.0 <1.8.1 | 1.7.4, 1.8.1 |
| github.com/envoyproxy/gatewaygo | >=1.8.0-rc.0,<1.8.1 | 1.8.1 |
| github.com/envoyproxy/gatewaygo | <1.7.4 | 1.7.4 |
| github.com/envoyproxy/gatewaygo | >=1.8.0-rc.0 <1.8.1 | 1.8.1 |
| github.com/envoyproxy/gatewaygo | >=0 <1.7.4 | 1.7.4 |
| github.com/envoyproxy/gatewaygo | >=0 <1.7.4 >=1.8.0-rc.0 <1.8.1 | 1.7.4, 1.8.1 |
Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 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, 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.
Quoted source text, attributed separately from HOL analysis.