# CVE-2026-44774: Traefik: Gateway API TraefikService backend accepts rest@internal, allowing unauthorized exposure of the REST provider despite providers.rest.insecure=false > A low-privileged user can bypass REST provider security settings to gain unauthorized write access to Traefik's dynamic configuration. - **Severity:** Medium 6.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:H/SA:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 May 2026 - **Updated:** 13 Aug 2026 - **Also known as:** CLEANSTART-2026-PG87313, GHSA-96qj-4jj5-wcjc, GO-2026-5277, MINI-83q9-fgj2-hrmh, MINI-x259-rrhm-m8h3, MINI-xpwq-9wrg-q98c, openSUSE-SU-2026:10810-1, openSUSE-SU-2026:10811-1 ## What is CVE-2026-44774? CVE-2026-44774 is a medium-severity missing authorization vulnerability in Traefik Traefik, published on 15 May 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-15 (External Control of System or Configuration Setting), CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2026-44774? 11 open source packages ship an affected version, including github.com/traefik/traefik/v3, github.com/traefik/traefik and github.com/traefik/traefik/v2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/traefik/traefik/v3` | Go | All versions | 3.6.17, 3.7.1 | | `github.com/traefik/traefik/v3` | Go | All versions | 3.6.17 | | `github.com/traefik/traefik/v3` | Go | All versions | 3.6.17 | | `github.com/traefik/traefik/v3` | Go | From 3.7.0 | 3.7.1 | | `github.com/traefik/traefik/v3` | Go | From 3.7.0 | 3.7.1 | | `github.com/traefik/traefik` | Go | All versions | None | | `github.com/traefik/traefik` | Go | All versions to 1.7.34 | None | | `github.com/traefik/traefik` | Go | All versions to 1.7.34 | None | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.46 | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.46 | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.46 | | `traefik` | openSUSE:Tumbleweed | All versions | 3.6.17-1.1 | | `traefik2` | openSUSE:Tumbleweed | All versions | 2.11.46-1.1 | Products: Traefik Traefik. ## How do I fix CVE-2026-44774? Upgrade github.com/traefik/traefik/v3 to a fixed version for your release line: 3.6.17 or 3.7.1. ## Is CVE-2026-44774 being exploited? There is no known exploitation of CVE-2026-44774 in the wild and no public exploit code. ## Other vulnerabilities in Traefik Traefik - [CVE-2024-45410](https://insights.sbomify.com/CVE-2024-45410/): HTTP client can remove the X-Forwarded headers in Traefik (critical 9.8) - [CVE-2026-88877](https://insights.sbomify.com/CVE-2026-88877/): Traefik v3.7.0 Authentication Bypass via from-to-www-redirect (critical 9.3) - [CVE-2026-85595](https://insights.sbomify.com/CVE-2026-85595/): Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth (critical 9.3) - [CVE-2026-88007](https://insights.sbomify.com/CVE-2026-88007/): Traefik HTTP/3 Backend NTLM Connection Reuse (critical 9.1) - [CVE-2026-88009](https://insights.sbomify.com/CVE-2026-88009/): Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-44774 and fix it if it is affected. What it is: CVE-2026-44774 is a medium-severity missing authorization vulnerability in Traefik Traefik, published on 15 May 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-44774 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.6.17, 3.7.1 - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.6.17 - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.6.17 - github.com/traefik/traefik/v3 (Go): affected from 3.7.0; fixed in 3.7.1 - github.com/traefik/traefik/v3 (Go): affected from 3.7.0; fixed in 3.7.1 - github.com/traefik/traefik (Go): affected all versions; no fix listed - github.com/traefik/traefik (Go): affected all versions up to 1.7.34; no fix listed - github.com/traefik/traefik (Go): affected all versions up to 1.7.34; no fix listed - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.46 - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.46 - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.46 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-44774/ (Markdown: https://insights.sbomify.com/CVE-2026-44774/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44774 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44774 - OSV: https://osv.dev/vulnerability/CVE-2026-44774 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-44774/ Summaries are generated and may contain mistakes; the official description above is the record.