# CVE-2026-29777: Traefik has a kubernetes gateway rule injection via unescaped backticks in HTTPRoute match values > Attackers with HTTPRoute write access can inject rule tokens to bypass hostname constraints and redirect traffic to malicious backends. - **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Mar 2026 - **Updated:** 11 Mar 2026 - **Also known as:** GHSA-8q2w-wr49-whqj, GO-2026-4679, MINI-g8f9-rfjc-3fmc, MINI-jm7w-749h-gh8r, MINI-w6vg-3mm8-6834 ## What is CVE-2026-29777? CVE-2026-29777 is a medium-severity code injection vulnerability in Traefik Traefik, published on 11 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description Traefik is an HTTP reverse proxy and load balancer. Prior to 3.6.10, A tenant with write access to an HTTPRoute resource can inject backtick-delimited rule tokens into Traefik's router rule language via unsanitized header or query parameter match values. In shared gateway deployments, this can bypass listener hostname constraints and redirect traffic for victim hostnames to attacker-controlled backends. This vulnerability is fixed in 3.6.10. Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component) ## Which versions are affected by CVE-2026-29777? 9 open source packages ship an affected version, including github.com/traefik/traefik, github.com/traefik/traefik/v2 and github.com/traefik/traefik/v3. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `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 | None | | `github.com/traefik/traefik/v2` | Go | All versions to 2.11.40 | None | | `github.com/traefik/traefik/v2` | Go | All versions to 2.11.40 | None | | `github.com/traefik/traefik/v3` | Go | All versions | 3.6.10 | | `github.com/traefik/traefik/v3` | Go | All versions | 3.6.10 | | `github.com/traefik/traefik/v3` | Go | All versions | 3.6.10 | Products: Traefik Traefik. ## How do I fix CVE-2026-29777? Upgrade to a fixed version. ## Is CVE-2026-29777 being exploited? There is no known exploitation of CVE-2026-29777 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-29777 and fix it if it is affected. What it is: CVE-2026-29777 is a medium-severity code injection vulnerability in Traefik Traefik, published on 11 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-29777 in the wild and no public exploit code. Affected packages and fixed versions: - 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; no fix listed - github.com/traefik/traefik/v2 (Go): affected all versions up to 2.11.40; no fix listed - github.com/traefik/traefik/v2 (Go): affected all versions up to 2.11.40; no fix listed - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.6.10 - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.6.10 - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.6.10 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-29777/ (Markdown: https://insights.sbomify.com/CVE-2026-29777/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29777 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29777 - OSV: https://osv.dev/vulnerability/CVE-2026-29777 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-29777/ Summaries are generated and may contain mistakes; the official description above is the record.