Configuration takeover via permissive internal-service routing
Published May 15, 2026 · Updated May 15, 2026
Improper access control in Traefik Proxy before 2.11.46, 3.6.17, and 3.7.1 allows remote authenticated users to rewrite routing configuration. The Kubernetes Gateway provider accepts every TraefikService backend name ending in @internal, so a tenant-controlled HTTPRoute can publish the write-capable rest@internal handler despite providers.rest.insecure=false. Exploitation requires the Gateway and REST providers, a shared Gateway that accepts the tenant namespace, and permission to create or update HTTPRoute objects; successful use grants live control over routers and services.
Summary
What happened
Improper access control in Traefik Proxy before 2.11.46, 3.6.17, and 3.7.1 allows remote authenticated users to rewrite routing configuration. The Kubernetes Gateway provider accepts every TraefikService backend name ending in @internal, so a tenant-controlled HTTPRoute can publish the write-capable rest@internal handler despite providers.rest.insecure=false. Exploitation requires the Gateway and REST providers, a shared Gateway that accepts the tenant namespace, and permission to create or update HTTPRoute objects; successful use grants live control over routers and services.
The record
- CVE
- CVE-2026-44774
- Published
- May 15, 2026
- Updated
- May 15, 2026
- Vendor
- Traefik Labs
- Product
- Traefik Proxy
- Classifications
- CWE-284, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 15, 2026CVE publishedPublication date reported by the CVE source.
- May 15, 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=< 2.11.46
- Affected versionversion=>= 3.0.0-beta1, < 3.6.17
- Affected versionversion=>= 3.7.0-rc.0, < 3.7.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream rest@internal exposure 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