Critical [CVE-2026-65601] Privilege Escalation via Kubernetes Gateway API Namespace Confusion
This critical-severity Red Hat Linux advisory covers CVE-2026-65601 affecting Red Hat OpenShift Dev Spaces.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
Traefik versions 3.7.0 through 3.7.6 contain a namespace confusion vulnerability in the Kubernetes Gateway API provider. When resolving HTTPRoute.spec.rules[].backendRefs[].filters[].extensionRef, Traefik used the backend Service namespace instead of the HTTPRoute namespace.
A low-privileged route author holding a ReferenceGrant for a cross-namespace Service could therefore bind a Traefik Middleware from the backend namespace without a separate grant for that middleware, potentially injecting trusted reverse-proxy identity headers into downstream requests. The issue is fixed in version 3.7.7.
A flaw was found in Traefik, a cloud-native edge router. This flaw allows an attacker to bypass security controls by incorrectly binding a Traefik Middleware from a different namespace, potentially leading to the injection of trusted identity headers into network requests.
This could result in unauthorized access or privilege escalation within the Kubernetes cluster. This is an Important flaw in Traefik's Kubernetes Gateway API provider, affecting Red Hat OpenShift Dev Spaces.
A low-privileged user in a Kubernetes environment can exploit a namespace confusion vulnerability to bypass security controls. Red Hat severity: Important — CVSS 9.6 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N).
Weakness: CWE-348. Affected Red Hat products: Red Hat OpenShift Dev Spaces.
- 3.7.0
- 3.7.6
Official advisory · high-confidence parse· fetched 16 days ago·verify at source
Mitigation
Upgrade to a fixed release: 3.7.7. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 16 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.