Summary
Traefik has Knative Ingress Rule Injection that Allows Host Restriction Bypass
Impact
- Vulnerability type: Rule injection / authorization bypass at routing layer.
- Primary impact: Bypass of intended routing predicates (host/header/path), enabling unauthorized routing to protected services.
- Who is impacted: Primarily deployments using Traefik Knative provider where untrusted or semi-trusted actors can create/update Knative Ingress resources (typical in multi-tenant clusters, shared namespaces, or weak admission controls). Standard Kubernetes Ingress host injection is usually blocked by API validation.
- Security consequences: Cross-tenant traffic access, internal service exposure, policy bypass, and potential chaining with app-level vulnerabilities.
Affected versions
github.com/traefik/traefik/v3 (< 3.6.11)
github.com/traefik/traefik/v3 (>= 3.7.0-ea.1, < 3.7.0-ea.2)
github.com/traefik/traefik/v2 (<= 2.11.42)
Security releases
github.com/traefik/traefik/v3 → 3.6.11 (go)
github.com/traefik/traefik/v3 → 3.7.0-ea.2 (go)
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-32695? CVE-2026-32695 is a medium-severity security vulnerability in github.com/traefik/traefik/v3 (go), affecting versions < 3.6.11. It is fixed in 3.6.11, 3.7.0-ea.2.
- Which packages are affected by CVE-2026-32695?
github.com/traefik/traefik/v3(go) (versions < 3.6.11)github.com/traefik/traefik/v2(go) (versions <= 2.11.42)
- Is there a fix for CVE-2026-32695? Yes. CVE-2026-32695 is fixed in 3.6.11, 3.7.0-ea.2. Upgrade to this version or later.
- Is CVE-2026-32695 exploitable, and should I be worried? Whether CVE-2026-32695 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-32695 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-32695?
- Upgrade
github.com/traefik/traefik/v3to 3.6.11 or later - Upgrade
github.com/traefik/traefik/v3to 3.7.0-ea.2 or later
- Upgrade