CVE-2026-65601 traefik CVE debrief

Who should care

Users of Traefik versions 3.7.0 through 3.7.6, especially those using the Kubernetes Gateway API provider, should be aware of this vulnerability and take steps to mitigate it. This includes operators managing Traefik deployments, platform administrators responsible for Kubernetes environments, vulnerability management teams assessing exposure, and security teams verifying compensating controls.

Technical summary

The vulnerability is caused by Traefik's incorrect use of the backend Service namespace instead of the HTTPRoute namespace when resolving HTTPRoute.spec.rules[].backendRefs[].filters[].extensionRef. This can allow a low-privileged route author to bind a Traefik Middleware from the backend namespace without proper authorization, potentially leading to the injection of trusted reverse-proxy identity headers into downstream requests.

Defensive priority

Medium priority should be given to patching Traefik versions 3.7.0 through 3.7.6 due to the potential for namespace confusion and unauthorized access to sensitive resources.

Recommended defensive actions

• Patch Traefik to version 3.7.7 or later
• Review and update ReferenceGrants for cross-namespace Services
• Monitor for suspicious activity related to HTTPRoute and Middleware configurations
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record was published on 2026-07-22T12:18:20.430Z and has not been modified since then. The NVD entry is currently Undergoing Analysis. The vulnerability was disclosed by Vulncheck, and details can be found in their advisory.

Official resources