CVE-2026-44774: Traefik: Gateway API TraefikService backend accepts rest@internal, allowing unauthorized exposure of the REST provider despite providers.rest.insecure=false
Traefik is an HTTP reverse proxy and load balancer. Prior to 2.11.46, 3.6.17, and 3.7.1, Traefik's Kubernetes Gateway API provider allows a tenant with HTTPRoute creation permissions to expose the REST provider handler, bypassing the providers.rest.insecure=false setting. The Gateway provider accepts any TraefikService backend reference whose name ends with @internal, making it possible to route traffic to rest@internal in addition to the intended api@internal. In shared Gateway deployments where the REST provider is enabled, this allows a low-privileged actor to gain live dynamic configuration write access to Traefik, enabling unauthorized reconfiguration of routers and services. This vulnerability is fixed in 2.11.46, 3.6.17, and 3.7.1.
Security readout for executives and security teams
Plain-English summary
CVE-2026-44774 lets a Kubernetes tenant with HTTPRoute rights expose Traefik’s internal REST provider despite providers.rest.insecure=false. In shared Gateway deployments with the REST provider enabled, this can let a low-privileged actor change live Traefik routing configuration.
Executive priority
Prioritize remediation for multi-tenant Kubernetes ingress environments. The issue can turn limited route-management permissions into live proxy reconfiguration capability, creating meaningful outage and traffic-control risk.
Technical view
Affected Traefik Gateway API provider versions accept TraefikService backends whose names end in @internal. That permits routing to rest@internal, not only the intended api@internal. The impact is unauthorized dynamic configuration writes, with high integrity and availability impact. Fixed versions are 2.11.46, 3.6.17, and 3.7.1.
Likely exposure
Exposure is most likely in Kubernetes environments using Traefik Gateway API with shared tenant control, REST provider enabled, and delegated HTTPRoute creation permissions.
Exploitation context
The source bundle reports no CISA KEV listing and provides no evidence of active exploitation. Exploitation requires network access and low privileges in the form of HTTPRoute creation rights.
Researcher notes
The key boundary failure is overly broad acceptance of @internal TraefikService backends by the Gateway provider. Evidence supports affected version ranges and fixed releases, but the bundle does not include exploit telemetry or detailed patch diff analysis.
Mitigation direction
Upgrade Traefik to 2.11.46, 3.6.17, 3.7.1, or later.
Review vendor advisories for environment-specific remediation guidance.
Limit HTTPRoute creation rights in shared Gateway deployments until upgraded.
Assess whether the REST provider is enabled and required.
Audit tenant-controlled routes for internal TraefikService backend references.
Validation and detection
Inventory Traefik versions across Kubernetes Gateway API deployments.
Identify clusters where tenants can create HTTPRoutes.
Check whether the REST provider is enabled in those deployments.
Review HTTPRoute and TraefikService backend references for @internal targets.
Confirm upgraded deployments run a fixed Traefik version.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-15: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-15 · source CWE mapping
External Control of System or Configuration Setting
External Control of System or Configuration Setting represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.