Identity-header injection via cross-namespace middleware binding
Published Jul 22, 2026 · Updated Jul 22, 2026
Namespace confusion in Traefik Proxy 3.7.0 through 3.7.6 allows remote authenticated users to inject trusted identity headers. The Gateway API provider reuses the backend Service namespace when resolving an HTTPRoute backend ExtensionRef, binding a Middleware that the route namespace was not granted access to. The attack requires route-author capability and a cross-namespace Service ReferenceGrant; downstream identity spoofing occurs only when the selected Middleware sets headers trusted by the application.
Summary
What happened
Namespace confusion in Traefik Proxy 3.7.0 through 3.7.6 allows remote authenticated users to inject trusted identity headers. The Gateway API provider reuses the backend Service namespace when resolving an HTTPRoute backend ExtensionRef, binding a Middleware that the route namespace was not granted access to. The attack requires route-author capability and a cross-namespace Service ReferenceGrant; downstream identity spoofing occurs only when the selected Middleware sets headers trusted by the application.
The record
- CVE
- CVE-2026-65601
- Published
- Jul 22, 2026
- Updated
- Jul 22, 2026
- Vendor
- Traefik Labs
- Product
- Traefik Proxy
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 22, 2026CVE publishedPublication date reported by the CVE source.
- Jul 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.7.0 <3.7.7
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Gateway API BackendRef ExtensionRef namespace-confusion proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo