CVE-2024-52003: V2 · Traefik's X-Forwarded-Prefix Header still allows for Open Redirect
Affects github.com/traefik/traefik/v2Source GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.11.14 when convenient.
Data as of 19 Nov 2026, 02:13 UTC
- Patch
- Available – fixed in 2.11.14, 3.2.1
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade github.com/traefik/traefik/v2 to 2.11.14; github.com/traefik/traefik/v3 to 3.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/traefik/traefik/v2 | Affected
| Fixed in
|
| Gogithub.com/traefik/traefik/v3 | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
### Impact There is a vulnerability in Traefik that allows the client to provide the `X-Forwarded-Prefix` header from an untrusted source. ### Patches - https://github.com/traefik/traefik/releases/tag/v2.11.14 - https://github.com/traefik/traefik/releases/tag/v3.2.1 ### Workarounds No workaround. ### For more information If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues). <details> <summary>Original Description</summary> ### Summary The previously reported open redirect ([GHSA-6qq8-5wq3-86rp](https://github.com/traefik/traefik/security/advisories/GHSA-6qq8-5wq3-86rp)) is not fixed correctly. The safePrefix function can be tricked to return an absolute URL. ### Details The Traefik API [dashboard component](https://github.com/traefik/traefik/blob/master/pkg/api/dashboard/dashboard.go) tries to validate that the value of the header X-Forwarded-Prefix is a site relative path: ```go http.Redirect(resp, req, safePrefix(req)+"/dashboard/", http.StatusFound) ``` ```go func safePrefix(req *http.Request) string { prefix := req.Header.Get("X-Forwarded-Prefix") if prefix == "" { return "" } parse, err := url.Parse(prefix) if err != nil { return "" } return parse.Path } ``` ### PoC An attacker can bypass this by sending the following payload: ```bash curl -v 'http://traefik.localhost' -H 'X-Forwarded-Prefix: %0d//a.com' [...] > HTTP/1.1 302 Found > Location: //a.com/dashboard/ ``` or similar: ```bash curl -v 'http://traefik.localhost' -H 'X-Forwarded-Prefix: %2f%2fa.com' [...] > HTTP/1.1 302 Found > Location: //a.com/dashboard/ ``` ### Impact Similar to the previously reported bug. In cache poisoning scenarios this may be exploitable. </details>
References
- github.com/traefik/traefik/security/advisories/GHSA-h924-8g65-j9wg (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2024-52003 (opens in a new tab)
- github.com/traefik/traefik/pull/11253 (opens in a new tab)
- github.com/traefik/traefik (opens in a new tab)
- github.com/traefik/traefik/releases/tag/v2.11.14 (opens in a new tab)
- github.com/traefik/traefik/releases/tag/v3.2.1 (opens in a new tab)