Incorrect Authorization Affecting github.com/traefik/traefik/pkg/provider/kubernetes/gateway package, versions >=3.7.0 <3.7.7
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Incorrect Authorization vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMTRAEFIKTRAEFIKPKGPROVIDERKUBERNETESGATEWAY-18601993
- published10 Aug 2026
- disclosed5 Aug 2026
- creditCuB3y0nd
Introduced: 5 Aug 2026
CVE-2026-65601 (opens in a new tab)How to fix?
Upgrade github.com/traefik/traefik/pkg/provider/kubernetes/gateway to version 3.7.7 or higher.
Overview
Affected versions of this package are vulnerable to Incorrect Authorization through improper namespace resolution in the extensionRef process. An attacker can cause unauthorized middleware from a backend namespace to be bound to a route by crafting a malicious HTTPRoute with cross-namespace backend references. This can result in attacker-controlled headers being injected into requests, potentially allowing the attacker to impersonate users or escalate privileges in downstream applications that trust such headers. This is only exploitable if the attacker has low-privileged route author permissions and a ReferenceGrant exists for a cross-namespace Service reference.
Workaround
This vulnerability can be mitigated by avoiding granting untrusted namespaces permission to attach HTTPRoute objects to shared Gateways that route to sensitive backends, not placing privileged or identity-bearing Middleware objects in namespaces accessible by untrusted cross-namespace backend references, preferring route-local filters, auditing usage of backendRef extensionRefs, and stripping trusted reverse-proxy identity headers at backend application boundaries unless originating from a dedicated authentication gateway.