Bug 2533373 (CVE-2026-53718) - CVE-2026-53718 github.com/envoyproxy/gateway: Envoy Gateway: Cross-namespace authorization bypass
Summary: CVE-2026-53718 github.com/envoyproxy/gateway: Envoy Gateway: Cross-namespace ...
Keywords:
Status: NEW
Alias: CVE-2026-53718
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-14 20:31 UTC by OSIDB Bzimport
Modified: 2026-09-30 16:33 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-14 20:31:23 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.