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
A tenant allowed to create Kubernetes HTTPRoutes could expose Traefik’s normally protected REST interface. In shared deployments, this could let a low-privileged user change live routing and service configuration, potentially disrupting traffic or exposing data. Risk requires the Gateway API provider and enabled REST provider.
Executive priority
Treat as a high-priority upgrade for multi-tenant or delegated Kubernetes environments. The vulnerability crosses an intended security boundary and can affect traffic integrity and availability. Accelerate remediation where untrusted teams can create HTTPRoutes; validate configuration before downgrading priority elsewhere.
Technical view
Affected Traefik Gateway API versions accept TraefikService backend names ending in @internal, permitting rest@internal instead of only the intended api@internal. This bypasses providers.rest.insecure=false and can provide dynamic configuration write access. CVSS 3.1 is 8.3, reflecting network reachability, low complexity, limited privileges, and high integrity and availability impact.
Likely exposure
Exposure is most likely in shared Kubernetes Gateway deployments running Traefik before 2.11.46, 3.6.17, or 3.7.1, with the REST provider enabled and tenants able to create HTTPRoutes. Deployments without those conditions are not shown as exploitable by the supplied evidence.
Exploitation context
The supplied record does not establish active exploitation, and the CVE is not listed as KEV. Exploitation requires an actor with HTTPRoute creation permission; it is not described as unauthenticated. Successful abuse could enable unauthorized changes to routers and services through the exposed REST handler.
Researcher notes
The flaw is an authorization and configuration-validation failure, mapped to CWE-15 and CWE-284. The supplied evidence identifies backend-name suffix acceptance as the bypass. It does not provide evidence of public exploitation, affected configurations beyond those stated, or compromise indicators specific to this CVE.
Mitigation direction
Upgrade to Traefik 2.11.46, 3.6.17, 3.7.1, or a later supported release.
Prioritize shared Gateway deployments where tenants can create HTTPRoutes.
Until upgraded, restrict HTTPRoute creation permissions to trusted administrators.
Disable the REST provider if operationally unnecessary, following vendor guidance.
Review Traefik and Red Hat advisories for platform-specific remediation details.
Validation and detection
Inventory Traefik versions across Kubernetes Gateway deployments.
Confirm whether the Gateway API provider and REST provider are enabled.
Identify principals permitted to create or modify HTTPRoutes.
Review HTTPRoutes for TraefikService references ending in @internal, especially rest@internal.
Verify upgraded instances report a fixed or later supported version.
Audit recent routing and service changes for unauthorized reconfiguration.
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.