Internal service exposure via wrong namespace check
Published Jun 23, 2026 · Updated Jun 23, 2026
Incorrect authorization in Traefik Proxy before 3.6.21 and 3.7.0-ea.1 through 3.7.4 allows remote authenticated users to expose internal services. The Kubernetes Gateway WRR path replaces the HTTPRoute namespace with backendRef.namespace before checking crossProviderNamespaces. Exploitation requires an accepted multi-backend HTTPRoute and a matching ReferenceGrant; exposed services can include the API, dashboard, or REST handler.
Summary
What happened
Incorrect authorization in Traefik Proxy before 3.6.21 and 3.7.0-ea.1 through 3.7.4 allows remote authenticated users to expose internal services. The Kubernetes Gateway WRR path replaces the HTTPRoute namespace with backendRef.namespace before checking crossProviderNamespaces. Exploitation requires an accepted multi-backend HTTPRoute and a matching ReferenceGrant; exposed services can include the API, dashboard, or REST handler.
The record
- CVE
- CVE-2026-54761
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- Traefik Labs
- Product
- Traefik Proxy
- Classifications
- CWE-863, CWE-284, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 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.6.21
- Affected versionversion=>= 3.7.0-ea.1, < 3.7.5
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
- Self-contained kind-cluster 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