Is CVE-2026-53715 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53715 being exploited in the wild.

How severe is CVE-2026-53715?

Medium severity, with a CVSS score of 5.3, published 14 September 2026.

Which products and versions are affected?

github.com/envoyproxy/gateway (Go) SEMVER:introduced=0,fixed=1.7.4,introduced=1.8.0-rc.0,fixed=1.8.1, SEMVER:introduced=1.8.0-rc.0,fixed=1.8.1.

Is there a fix for CVE-2026-53715?

Yes. github.com/envoyproxy/gateway (Go): upgrade to 1.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53715 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-53715?

Check whether you run github.com/envoyproxy/gateway (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53715: Envoy Gateway race condition in Wasm cache ServeHTTP

CVE-2026-53715 · Severity: medium · CVSS 5.3 · Published 2026-09-14

Envoy Gateway is a tool used to manage network traffic and security policies for applications. A flaw in how it handles internal data for WebAssembly (Wasm) modules can allow an attacker to crash the gateway's control system. This results in a service outage (Denial of Service), though the system is typically configured to restart automatically.

Technologies: github.com/envoyproxy/gateway (Go). Vendors: Go.

Quick answers

Is CVE-2026-53715 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53715 being exploited in the wild.
How severe is CVE-2026-53715?: Medium severity, with a CVSS score of 5.3, published 14 September 2026.
Which products and versions are affected?: github.com/envoyproxy/gateway (Go) SEMVER:introduced=0,fixed=1.7.4,introduced=1.8.0-rc.0,fixed=1.8.1, SEMVER:introduced=1.8.0-rc.0,fixed=1.8.1.
Is there a fix for CVE-2026-53715?: Yes. github.com/envoyproxy/gateway (Go): upgrade to 1.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53715 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53715?: Check whether you run github.com/envoyproxy/gateway (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/envoyproxy/gateway (Go): upgrade to 1.8.1 or later
```
go get github.com/envoyproxy/gateway@v1.8.1
```

Technical details

A race condition exists in `httpserver.go` within the Envoy Gateway Wasm cache component. The `ServeHTTP` function performs an un-synchronized read of the `mappingPath2Cache` map at line 153, while concurrent writes occur under a lock at lines 201/209. Because Go's runtime throws an unrecoverable error when it detects concurrent map read/writes, the controller process terminates. An attacker with the ability to create `EnvoyExtensionPolicy` objects can trigger this by rapidly updating Wasm URLs while simultaneously flooding the HTTP server on port 18002. The vulnerability is patched in versions 1.7.4 and 1.8.1.

Affected products

Envoy Proxy gateway >= 1.8.0-rc.0, < 1.8.1; < 1.7.4

Identifiers

CVE-2026-53715
GHSA-8fv2-88gg-hm7q
GO-2026-6005

Timeline

2026-06-05: disclosed: Initial disclosure by zirain
2026-07-16: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.