Traefik's X-Forwarded-Prefix Header still allows for Open Redirect

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2024-52003: 0.40% estimated exploitation activity in the next 30 days; percentile 34.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. <details <summaryOriginal Description</summary Summary The previously reported open redirect (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 tries to validate that the value of the header X-Forwarded-Prefix is a site relative path: PoC An attacker can bypass this by sending the following payload: or similar: Impact Similar to the previously reported bug. In cache poisoning scenarios this may be exploitable. </details

Published by the source

2 Dec 2024, 17:12 UTC

Last modified by the source

27 Nov 2025, 08:05 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h924-8g65-j9wg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-52003

Advisory: Traefik's X-Forwarded-Prefix Header still allows for Open Redirect
IDs: CVE-2024-52003, GHSA-h924-8g65-j9wg
Record: https://patchnext.com/advisories/cve-2024-52003 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
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.2.1; github.com/traefik/traefik/v2 2.11.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/traefik/traefik/v3: affected < 3.2.1; fixed in 3.2.1
- Go github.com/traefik/traefik/v2: affected < 2.11.14; fixed in 2.11.14

## 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-h924-8g65-j9wg (GitHub-reviewed advisory GHSA-h924-8g65-j9wg lists affected ranges: Go github.com/traefik/traefik/v2 >=0 =0 <3.2.1)

Commands are suggestions: review each one before running it.