CVE-2026-53715: Envoy Gateway Wasm Cache ServeHTTP Reads MappingPath2Cache Vulnerability
MODERATECVE-2026-53715 is a MODERATE (CVSS 5.3) wasm cache servehttp reads mappingpath2cache vulnerability (CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) affecting Envoy Gateway libraries in the Go ecosystem. The issue involves wasm cache servehttp reads mappingpath2cache without lock. Remediation is available by upgrading affected packages to version 1.8.1, 1.7.4.
CVE-2026-53715 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2026-53715
To remediate this vulnerability, upgrade all affected Envoy Gateway dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/envoyproxy/gateway to 1.8.1
Upgrade github.com/envoyproxy/gateway to 1.7.4
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/envoyproxy/gateway
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-53715, inspect your project dependencies for Envoy Gateway:
inspect dependencies for github.com/envoyproxy/gateway
Analyze the terminal output to locate any version of Envoy Gateway in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.8.1), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), where 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. In Envoy Gateway, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-53715 Affected Envoy Gateway Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/envoyproxy/gateway
|
Go |
≥ 1.8.0-rc.0
< 1.8.1
|
1.8.1
|
|
github.com/envoyproxy/gateway
|
Go |
< 1.7.4
|
1.7.4
|
References
Frequently Asked Questions
What is CVE-2026-53715?
Which Envoy Gateway versions are affected?
What version fixes CVE-2026-53715?
Is github.com/envoyproxy/gateway affected?
What is the CVSS score of CVE-2026-53715?
What CWE is associated with CVE-2026-53715?
How can I check Go dependencies for CVE-2026-53715?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8fv2-88gg-hm7q",
"modified" : "2026-07-16T19:21:15Z",
"published" : "2026-07-16T19:21:15Z",
"aliases" : [ "CVE-2026-53715" ],
"summary" : "Envoy Gateway: Wasm cache ServeHTTP reads mappingPath2Cache without lock",
"details" : "Vulnerability report without repro case. Repro case may be added later after harness is complete.\n\n**Preconditions (4):**\n- Pod-network reachability to :18002 (no auth)\n- Tenant can create EnvoyExtensionPolicy (baseline)\n- Attacker pod floods GET while churning EnvoyExtensionPolicy with distinct Wasm URLs\n- Read at :153 must overlap a write at :201/:209 (probabilistic, attacker controls both rates)\n\n**Description:**\n\nhttpserver.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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/envoyproxy/gateway"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.8.0-rc.0"
}, {
"fixed" : "1.8.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/envoyproxy/gateway"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.7.4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/envoyproxy/gateway/security/advisories/GHSA-8fv2-88gg-hm7q"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/envoyproxy/gateway"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-362" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-16T19:21:15Z",
"nvd_published_at" : null
}
}