# CVE-2026-32695: Traefik has Knative Ingress Rule Injection that Allows Host Restriction Bypass > Traefik's Knative provider allows rule injection via unescaped host values, enabling host restriction bypass and cross-tenant traffic exposure in multi-tenant clusters. - **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`) - **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:** 27 Mar 2026 - **Updated:** 15 Jul 2026 - **Also known as:** ECHO-8b5a-8e18-7ee1, GHSA-67jx-r9pv-98rj, GO-2026-4880, MINI-439x-vfxf-9hpw, MINI-5jj8-r99g-fhwr, MINI-qf35-mgf8-5m2q ## What is CVE-2026-32695? CVE-2026-32695 is a medium-severity code injection vulnerability in Traefik Traefik, published on 27 Mar 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 versions 3.6.11 and 3.7.0-ea.2, Traefik's Knative provider builds router rules by interpolating user-controlled values into backtick-delimited rule expressions without escaping. In live cluster validation, Knative `rules[].hosts[]` was exploitable for host restriction bypass (for example `tenant.example.com`) || Host(`attacker.com`), producing a router that serves attacker-controlled hosts. Knative `headers[].exact` also allows rule-syntax injection and proves unsafe rule construction. In multi-tenant clusters, this can route unauthorized traffic to victim services and lead to cross-tenant traffic exposure. Versions 3.6.11 and 3.7.0-ea.2 patch the issue. Weakness: CWE-917 (Improper Neutralization of Special Elements used in an Expression Language Statement), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component) ## Which versions are affected by CVE-2026-32695? 9 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.11, 3.7.0-ea.2 | | `github.com/traefik/traefik/v3` | Go | All versions | 3.6.11 | | `github.com/traefik/traefik/v3` | Go | All versions | 3.6.11 | | `github.com/traefik/traefik/v3` | Go | From 3.7.0-ea.1 | 3.7.0-ea.2 | | `github.com/traefik/traefik/v3` | Go | From 3.7.0-ea.1 | 3.7.0-ea.2 | | `github.com/traefik/traefik` | Go | All versions | None | | `github.com/traefik/traefik/v2` | Go | All versions | None | | `github.com/traefik/traefik/v2` | Go | All versions to 2.11.42 | None | | `github.com/traefik/traefik/v2` | Go | All versions to 2.11.42 | None | Products: Traefik Traefik. ## How do I fix CVE-2026-32695? Upgrade github.com/traefik/traefik/v3 to a fixed version for your release line: 3.6.11 or 3.7.0-ea.2. ## Is CVE-2026-32695 being exploited? There is no known exploitation of CVE-2026-32695 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-32695 and fix it if it is affected. What it is: CVE-2026-32695 is a medium-severity code injection vulnerability in Traefik Traefik, published on 27 Mar 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-32695 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.11, 3.7.0-ea.2 - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.6.11 - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.6.11 - github.com/traefik/traefik/v3 (Go): affected from 3.7.0-ea.1; fixed in 3.7.0-ea.2 - github.com/traefik/traefik/v3 (Go): affected from 3.7.0-ea.1; fixed in 3.7.0-ea.2 - github.com/traefik/traefik (Go): affected all versions; 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.42; no fix listed - github.com/traefik/traefik/v2 (Go): affected all versions up to 2.11.42; no fix listed 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-32695/ (Markdown: https://insights.sbomify.com/CVE-2026-32695/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32695 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32695 - OSV: https://osv.dev/vulnerability/CVE-2026-32695 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32695/ Summaries are generated and may contain mistakes; the official description above is the record.