GHSA-6qq8-5wq3-86rp
MEDIUMTraefik vulnerable to Open Redirect via handling of X-Forwarded-Prefix header
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
github.com/traefik/traefik🐹github.com/traefik/traefik/v2🐹github.com/containous/traefik🐹github.com/containous/traefik/v2🐹github.com/traefik/traefik/v2🐹github.com/containous/traefik/v2🐹github.com/traefik/traefik/api🐹github.com/traefik/traefik/v2/pkg/api+4 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
There exists a potential open redirect vulnerability in Traefik's handling of the X-Forwarded-Prefix header. 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.
Details
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.
e.g.
$ curl --header 'Host:traefik.localhost' --header 'X-Forwarded-Prefix:https://example.org' 'http://localhost:8081'
<a href="https://example.org/dashboard/">Found</a>.`
Impact
A successful exploitation of an open redirect can be used to entice victims to disclose sensitive information.
Workarounds
By using the headers middleware, the request header X-Forwarded-Prefix value can be overridden by the value . (dot)
- https://docs.traefik.io/v2.2/middlewares/headers/#customrequestheaders
- https://docs.traefik.io/v1.7/basics/#custom-headers
For more information
If you have any questions or comments about this advisory, open an issue in Traefik.
Credit
This issue was found by the GitHub Application Security Team and reported on behalf of the GHAS by the GitHub Security Lab Team.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/traefik/traefik | ≥ 1.5.0-rc5&&< 1.7.26 | 1.7.26 |
| 🐹Go | github.com/traefik/traefik/v2 | all versions | 2.3.0-rc6 |
| 🐹Go | github.com/containous/traefik | ≥ 1.5.0-rc5&&< 1.7.26 | 1.7.26 |
| 🐹Go | github.com/containous/traefik/v2 | all versions | 2.2.8 |
| 🐹Go | github.com/traefik/traefik/v2 | ≥ 2.3.0-rc1&&< 2.3.0-rc6 | 2.3.0-rc6 |
| 🐹Go | github.com/containous/traefik/v2 | ≥ 2.3.0-rc1&&< 2.3.0-rc3 | 2.3.0-rc3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/traefik/traefik. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/traefik/traefik to 1.7.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6qq8-5wq3-86rp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6qq8-5wq3-86rp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-6qq8-5wq3-86rp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6qq8-5wq3-86rp in your dependencies?
O3 detects GHSA-6qq8-5wq3-86rp across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.