CVE-2026-53718: envoyproxy gateway · Missing Authorization
Affects envoyproxy gatewaySource CVE Database V5
Not known to be exploited · CVSS 6.4 Medium : upgrade to 1.8.1 or 1.7.4 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% 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:H/I:L/A:LExploitation 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 29 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
Upgrade Envoy Gateway to version 1.7.4 or later, or to version 1.8.1 or later. These versions include the fix that enforces proper cross-namespace authorization checks for backendRef usage in HTTPRoute resources. No other mitigation is required as the issue is addressed by the official fix.
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, an HTTPRoute can use an extension-managed custom backendRef to reference a backend resource in another namespace without a matching Gateway API ReferenceGrant in the target namespace. The custom-backend branch in internal/gatewayapi/route.go omits validateBackendNamespace, allowing the route-owning namespace to bind to and use the resource without the backend namespace owner's consent and violating the Gateway API cross-namespace authorization model. This issue is fixed in versions 1.7.4 and 1.8.1.
References
- github.com/envoyproxy/gateway/security/advisories/GHSA-fcrp-7gc2-93g7 (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)