# CVE-2020-15129: Open redirect in Traefik > Traefik's API dashboard allows open redirects via the X-Forwarded-Prefix header, potentially exposing users to phishing or cache poisoning attacks. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 30 Jul 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-6qq8-5wq3-86rp ## What is CVE-2020-15129? CVE-2020-15129 is a medium-severity vulnerability in Traefik Traefik, published on 30 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description In Traefik before versions 1.7.26, 2.2.8, and 2.3.0-rc3, there exists a potential open redirect vulnerability in Traefik's handling of the "X-Forwarded-Prefix" header. The Traefik API dashboard component doesn't validate that the value of the header "X-Forwarded-Prefix" is a site relative path and will redirect to any header provided URI. Successful exploitation of an open redirect can be used to entice victims to disclose sensitive information. Active Exploitation of this issue is unlikely as it would require active header injection, however the Traefik team addressed this issue nonetheless to prevent abuse in e.g. cache poisoning scenarios. Weakness: CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2020-15129? 24 open source packages ship an affected version, including github.com/containous/traefik/v2, github.com/containous/traefik and github.com/containous/traefik/api. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/containous/traefik/v2` | Go | All versions | 2.2.8 | | `github.com/containous/traefik/v2` | Go | All versions | 2.2.8 | | `github.com/containous/traefik/v2` | Go | From 2.3.0-rc1 | 2.3.0-rc3 | | `github.com/containous/traefik/v2` | Go | From 2.3.0-rc1 | 2.3.0-rc3 | | `github.com/containous/traefik` | Go | From 1.5.0-rc5 | 1.7.26 | | `github.com/containous/traefik` | Go | From 1.5.0-rc5 | 1.7.26 | | `github.com/containous/traefik/api` | Go | From 1.5.0-rc5 | 1.7.26 | | `github.com/containous/traefik/api` | Go | From 1.5.0-rc5 | 1.7.26 | | `github.com/containous/traefik/v2/pkg/api` | Go | All versions | 2.2.8 | | `github.com/containous/traefik/v2/pkg/api` | Go | All versions | 2.2.8 | | `github.com/containous/traefik/v2/pkg/api` | Go | From 2.3.0-rc1 | 2.3.0-rc3 | | `github.com/containous/traefik/v2/pkg/api` | Go | From 2.3.0-rc1 | 2.3.0-rc3 | | `github.com/traefik/traefik` | Go | From 1.5.0-rc5 | 1.7.26 | | `github.com/traefik/traefik` | Go | From 1.5.0-rc5 | 1.7.26 | | `github.com/traefik/traefik/api` | Go | From 1.5.0-rc5 | 1.7.26 | | `github.com/traefik/traefik/api` | Go | From 1.5.0-rc5 | 1.7.26 | | `github.com/traefik/traefik/v2` | Go | All versions | 2.3.0-rc6 | | `github.com/traefik/traefik/v2` | Go | All versions | 2.3.0-rc6 | | `github.com/traefik/traefik/v2` | Go | From 2.3.0-rc1 | 2.3.0-rc6 | | `github.com/traefik/traefik/v2` | Go | From 2.3.0-rc1 | 2.3.0-rc6 | | `github.com/traefik/traefik/v2/pkg/api` | Go | All versions | 2.3.0-rc6 | | `github.com/traefik/traefik/v2/pkg/api` | Go | All versions | 2.3.0-rc6 | | `github.com/traefik/traefik/v2/pkg/api` | Go | From 2.3.0-rc1 | 2.3.0-rc6 | | `github.com/traefik/traefik/v2/pkg/api` | Go | From 2.3.0-rc1 | 2.3.0-rc6 | Products: Traefik Traefik. ## How do I fix CVE-2020-15129? Upgrade github.com/containous/traefik/v2 to a fixed version for your release line: 2.2.8 or 2.3.0-rc3. ## Is CVE-2020-15129 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-15129 exists. Public exploit code: - Traefik - Open Redirect (nuclei): http/cves/2020/CVE-2020-15129.yaml ## 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-2020-15129 and fix it if it is affected. What it is: CVE-2020-15129 is a medium-severity vulnerability in Traefik Traefik, published on 30 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-15129 exists. Affected packages and fixed versions: - github.com/containous/traefik/v2 (Go): affected all versions; fixed in 2.2.8 - github.com/containous/traefik/v2 (Go): affected all versions; fixed in 2.2.8 - github.com/containous/traefik/v2 (Go): affected from 2.3.0-rc1; fixed in 2.3.0-rc3 - github.com/containous/traefik/v2 (Go): affected from 2.3.0-rc1; fixed in 2.3.0-rc3 - github.com/containous/traefik (Go): affected from 1.5.0-rc5; fixed in 1.7.26 - github.com/containous/traefik (Go): affected from 1.5.0-rc5; fixed in 1.7.26 - github.com/containous/traefik/api (Go): affected from 1.5.0-rc5; fixed in 1.7.26 - github.com/containous/traefik/api (Go): affected from 1.5.0-rc5; fixed in 1.7.26 - github.com/containous/traefik/v2/pkg/api (Go): affected all versions; fixed in 2.2.8 - github.com/containous/traefik/v2/pkg/api (Go): affected all versions; fixed in 2.2.8 - github.com/containous/traefik/v2/pkg/api (Go): affected from 2.3.0-rc1; fixed in 2.3.0-rc3 - github.com/containous/traefik/v2/pkg/api (Go): affected from 2.3.0-rc1; fixed in 2.3.0-rc3 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-2020-15129/ (Markdown: https://insights.sbomify.com/CVE-2020-15129/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-15129 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-15129 - OSV: https://osv.dev/vulnerability/CVE-2020-15129 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-15129/ Summaries are generated and may contain mistakes; the official description above is the record.