# CVE-2024-52003: X-Forwarded-Prefix Header still allows for Open Redirect in traefik

> Traefik allows open redirects via the X-Forwarded-Prefix header, enabling attackers to redirect users to malicious sites.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Nov 2024
- **Updated:** 2 Dec 2024
- **Also known as:** ECHO-9eb7-a106-97d7, GHSA-h924-8g65-j9wg, GO-2024-3299

## What is CVE-2024-52003?

CVE-2024-52003 is a medium-severity vulnerability in Traefik Traefik, published on 29 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Traefik (pronounced traffic) is an HTTP reverse proxy and load balancer. There is a vulnerability in Traefik that allows the client to provide the X-Forwarded-Prefix header from an untrusted source. This issue has been addressed in versions 2.11.14 and 3.2.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2024-52003?

7 open source packages ship an affected version, including github.com/traefik/traefik/v2, github.com/traefik/traefik and github.com/traefik/traefik/v3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.11.14 |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.11.14 |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.11.14 |
| `github.com/traefik/traefik` | Go | All versions | None |
| `github.com/traefik/traefik/v3` | Go | All versions | 3.2.1 |
| `github.com/traefik/traefik/v3` | Go | All versions | 3.2.1 |
| `github.com/traefik/traefik/v3` | Go | All versions | 3.2.1 |

Products: Traefik Traefik.

## How do I fix CVE-2024-52003?

Upgrade github.com/traefik/traefik/v2 to 2.11.14 or later.

## Is CVE-2024-52003 being exploited?

There is no known exploitation of CVE-2024-52003 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-2024-52003 and fix it if it is affected.

What it is: CVE-2024-52003 is a medium-severity vulnerability in Traefik Traefik, published on 29 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-52003 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.14
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.14
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.14
- github.com/traefik/traefik (Go): affected all versions; no fix listed
- github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.2.1
- github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.2.1
- github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.2.1

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-2024-52003/ (Markdown: https://insights.sbomify.com/CVE-2024-52003/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-52003
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-52003
- OSV: https://osv.dev/vulnerability/CVE-2024-52003

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-52003/
Summaries are generated and may contain mistakes; the official description above is the record.