https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 14 Nov 2026 08:02:57 +0000 https://db.gcve.eu/vuln/cleanstart-2026-ni49374 <p><strong>Affected:</strong> CleanStart: tigera-operator</p> <p>Security vulnerability affects the tigera-operator package. This issue is resolved in later releases. See references for vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: tigera-operator</p> <p>Security vulnerability affects the tigera-operator package. This issue is resolved in later releases. See references for vulnerability details.</p> https://db.gcve.eu/vuln/cleanstart-2026-ni49374 https://db.gcve.eu/vuln/cve-2026-53718 <p><strong>Affected:</strong> envoyproxy gateway</p> <p>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&#39;s consent and violating the Gateway API cross-namespace authorization model. This issue is fixed in versions 1.7.4 and 1.8.1.</p> <p><strong>Affected:</strong> envoyproxy gateway</p> <p>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&#39;s consent and violating the Gateway API cross-namespace authorization model. This issue is fixed in versions 1.7.4 and 1.8.1.</p> https://db.gcve.eu/vuln/cve-2026-53718