CVE-2026-53715

Received Received - Intake

Race Condition in Envoy Gateway Leads to DoS

Publication date: 2026-09-14

Last updated on: 2026-09-14

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-14

Last Modified

2026-09-14

Generated

2026-09-15

AI Q&A

2026-09-15

EPSS Evaluated

N/A

NVD

CVE-2026-53715

Affected Vendors & Products

Vendor	Product	Version / Range
envoy	gateway	1.7.4
envoy	gateway	1.8.1
envoy	gateway	to 1.7.4\|end_excluding=1.8.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-362	The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

Executive Summary

This is a race condition in Envoy Gateway where concurrent read and write operations on a shared map can cause a denial of service. An attacker with network access can exploit this by sending many requests to trigger a crash in the controller process.

Detection Guidance

Detect this vulnerability by checking Envoy Gateway versions. Run: env | grep ENVOY_GATEWAY_VERSION or kubectl get pods -n <namespace> -o jsonpath='{.items[*].spec.containers[*].image}' to verify if versions are below 1.7.4 or 1.8.1.

Impact Analysis

If exploited, this vulnerability can cause the Envoy Gateway controller to crash, leading to a denial of service for the entire gateway. This disrupts traffic management and may require restarting the affected pod to restore functionality.

Mitigation Strategies

Upgrade Envoy Gateway to versions 1.7.4 or 1.8.1 or later immediately. Restrict network access to port 18002 to prevent unauthenticated access. Monitor controller logs for unexpected terminations.

Hi! I’m here to help you understand CVE-2026-53715. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70