traefik CVE-2024-45410 fix bypass: lowercase Connection tokens can delete traefik-managed forwarded identity headers (for example, X-Real-Ip)
CVE-2026-29054GHSA-92mv-8f8w-wq52
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/traefik/traefik/v3 3.6.9; github.com/traefik/traefik/v2 2.11.38), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/traefik/traefik/v3
- Affected
- >= 3.1.3, <= 3.6.8
- Fixed in
- 3.6.9
Go github.com/traefik/traefik/v2
- Affected
- >= 2.11.9, <= 2.11.37
- Fixed in
- 2.11.38
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-92mv-8f8w-wq52 lists affected ranges: Go github.com/traefik/traefik/v2 >=2.11.9 =3.1.3 <=3.6.8
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- EPSS
- CVE-2026-29054: 0.53% estimated exploitation activity in the next 30 days; percentile 44.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact There is a potential vulnerability in Traefik managing the Connection header with X-Forwarded headers. When Traefik processes HTTP/1.1 requests, the protection put in place to prevent the removal of Traefik-managed X-Forwarded headers (such as X-Real-Ip, X-Forwarded-Host, X-Forwarded-Port, etc.) via the Connection header does not handle case sensitivity correctly. The Connection tokens are compared case-sensitively against the protected header names, but the actual header deletion operates case-insensitively. As a result, a remote unauthenticated client can use lowercase Connection tokens (e.g. Connection: x-real-ip) to bypass the protection and trigger the removal of Traefik-managed forwarded identity headers. This is a bypass of the fix for CVE-2024-45410. Depending on the deployment, the impact may be higher if downstream services rely on these headers (such as X-Real-Ip or X-Forwarded-) for authentication, authorization, routing, or scheme decisions. Patches -…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-92mv-8f8w-wq52
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-29054 Advisory: traefik CVE-2024-45410 fix bypass: lowercase `Connection` tokens can delete traefik-managed forwarded identity headers (for example, `X-Real-Ip`) IDs: CVE-2026-29054, GHSA-92mv-8f8w-wq52 Record: https://patchnext.com/advisories/cve-2026-29054 (revision 1, source checked 26 Oct 2026, 15:15 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/traefik/traefik/v3 3.6.9; github.com/traefik/traefik/v2 2.11.38. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/traefik/traefik/v3: affected >= 3.1.3, <= 3.6.8; fixed in 3.6.9 - Go github.com/traefik/traefik/v2: affected >= 2.11.9, <= 2.11.37; fixed in 2.11.38 ## Suggested inspection (read-only) - Go github.com/traefik/traefik/v3: check the installed version with your package manager. - Go github.com/traefik/traefik/v2: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/traefik/traefik/v3, github.com/traefik/traefik/v2. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-92mv-8f8w-wq52 (GitHub-reviewed advisory GHSA-92mv-8f8w-wq52 lists affected ranges: Go github.com/traefik/traefik/v2 >=2.11.9 =3.1.3 <=3.6.8) Commands are suggestions: review each one before running it.
Loading voting…