Cross-namespace backend access via omitted authorization check
Published Sep 14, 2026 · Updated Sep 14, 2026
Authorization bypass in Envoy Gateway before 1.7.4 and 1.8.0-rc.0 through 1.8.0 allows remote authenticated users to route traffic. The custom-backend branch in internal/gatewayapi/route.go skips validateBackendNamespace, so it never verifies the required ReferenceGrant. Reachability requires permission to create HTTPRoutes and enable extension-managed custom backends; the bypass grants cross-namespace use without the backend owner's consent.
Summary
What happened
Authorization bypass in Envoy Gateway before 1.7.4 and 1.8.0-rc.0 through 1.8.0 allows remote authenticated users to route traffic. The custom-backend branch in internal/gatewayapi/route.go skips validateBackendNamespace, so it never verifies the required ReferenceGrant. Reachability requires permission to create HTTPRoutes and enable extension-managed custom backends; the bypass grants cross-namespace use without the backend owner's consent.
The record
- CVE
- CVE-2026-53718
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Envoy Proxy
- Product
- Envoy Gateway
- Classifications
- CWE-862, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.7.4
- Affected versionversion=>= 1.8.0-rc.0, < 1.8.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo