dbcve.org
TraefikApplication

CVE-2026-29777

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 3.6.10 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Traefik versions before 3.6.10 contain an injection vulnerability in the router rule language. Tenants with write access to HTTPRoute resources can inject backtick-delimited rule tokens through unsanitized header or query parameter match values. In shared gateway deployments, this allows attackers to bypass listener hostname constraints and redirect traffic from victim hostnames to attacker-controlled backends.

MitigationUpgrade Traefik to version 3.6.10 or later. Additionally, review and validate HTTPRoute configurations to ensure header and query parameter match values are properly sanitized before deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TraefikApplication
Affected:< 3.6.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Traefik version
    Run 'traefik version' or inspect the Traefik Docker image tag, Helm chart version, or Kubernetes deployment manifest to determine the installed version
    Affected if The installed version is before 3.6.10 (any 3.x version below 3.6.10, or any 2.x version)
  2. Confirm HTTPRoute usage
    List all HTTPRoute resources in the cluster using 'kubectl get httproute -A' or inspect YAML manifests in your configuration repository
    Affected if HTTPRoute resources are defined and applied in the environment
  3. Identify header match rules
    Inspect each HTTPRoute for 'match' entries under 'headerMatches' and check if 'value' fields contain any backtick characters (`)
    Affected if Any HTTPRoute contains headerMatches with values that include backtick characters
  4. Identify query parameter match rules
    Inspect each HTTPRoute for 'match' entries under 'queryParamMatches' and check if 'value' fields contain any backtick characters (`)
    Affected if Any HTTPRoute contains queryParamMatches with values that include backtick characters

You are affected if running Traefik version below 3.6.10 AND you have HTTPRoute resources with header or query parameter match values containing backtick characters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.6.10 or later
Fixed in 3.6.10
Interim mitigation

Upgrade Traefik to version 3.6.10 or later. Additionally, review and validate HTTPRoute configurations to ensure header and query parameter match values are properly sanitized before deployment.

Recommended fix High confidence

Traefik 3.6.10

  1. Identify your current Traefik version using `traefik --version`
  2. Review the Traefik 3.6.10 release notes for any migration or configuration changes
  3. Plan a maintenance window for the upgrade
  4. Backup your current Traefik configuration files
  5. Stop the running Traefik instance
  6. Install Traefik version 3.6.10 using your package manager or by downloading the binary from the official releases
  7. Verify the new binary version using `traefik --version`
  8. Restore or update your configuration files as needed based on 3.6.10 release notes
Caveat Review 3.6.10 release notes; no specific breaking changes mentioned in the provided description

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Traefik Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29777 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data