Summary
Traefik: Gateway API TraefikService backend accepts rest@internal, allowing unauthorized exposure of the REST provider despite providers.rest.insecure=false
Impact
This is an authorization / trust-boundary bypass affecting shared Gateway deployments.
On affected deployments, an actor who should only be able to create or update HTTPRoute objects can escalate to live Traefik dynamic-configuration write access. That can allow unauthorized reconfiguration of routers and services, publication of additional internal surfaces, request interception or rerouting, and denial of service through destructive config changes.
On affected deployments, this gives a low-privileged Gateway route author live Traefik dynamic-configuration write access. This is critical for affected shared Gateway deployments because it can give a low-privileged route author live Traefik dynamic-configuration write access, but it depends on providers.rest being enabled.
This is not an unauthenticated vulnerability in all Traefik deployments. The issue depends on realistic but specific conditions:
providers.restmust be enabled- the attacker must be allowed to attach
HTTPRouteresources to a shared Gateway
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Frequently Asked Questions
- What is CVE-2026-44774? CVE-2026-44774 is a medium-severity security vulnerability in github.com/traefik/traefik/v3 (go), affecting versions = 3.7.0. It is fixed in 3.7.1, 3.6.17, 2.11.46.
- Which packages are affected by CVE-2026-44774?
github.com/traefik/traefik/v3(go) (versions = 3.7.0)github.com/traefik/traefik/v2(go) (versions <= 2.11.45)github.com/traefik/traefik(go) (versions <= 1.7.34)
- Is there a fix for CVE-2026-44774? Yes. CVE-2026-44774 is fixed in 3.7.1, 3.6.17, 2.11.46. Upgrade to this version or later.
- Is CVE-2026-44774 exploitable, and should I be worried? Whether CVE-2026-44774 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-44774 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-44774?
- Upgrade
github.com/traefik/traefik/v3to 3.7.1 or later - Upgrade
github.com/traefik/traefik/v3to 3.6.17 or later - Upgrade
github.com/traefik/traefik/v2to 2.11.46 or later
- Upgrade