BIT-envoy-gateway-2026-53718

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/envoy-gateway/BIT-envoy-gateway-2026-53718.json
JSON Data
https://api.test.osv.dev/v1/vulns/BIT-envoy-gateway-2026-53718
Aliases
Published
2026-09-21T08:54:59Z
Modified
2026-09-21T09:40:33Z
Summary
Envoy Gateway custom backendRef cross-namespace ReferenceGrant bypass
Details

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.

Database specific 
{
    "cpes":  [
        "cpe:2.3:a:envoyproxy:gateway:*:*:*:*:*:go:*:*"
    ],
    "severity":  "Medium"
}
References

Affected packages

Bitnami / envoy-gateway

Package

Name
envoy-gateway
Purl
pkg:bitnami/envoy-gateway

Severity

  • 6.4 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Fixed
1.7.4
Introduced
1.8.0
Fixed
1.8.1

Database specific

source 
"https://github.com/bitnami/vulndb/tree/main/data/envoy-gateway/BIT-envoy-gateway-2026-53718.json"