How severe is CVE-2020-15129?

CVE-2020-15129 has a CVSS score of 4.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-15129?

CVE-2020-15129 affects the following packages: github.com/traefik/traefik (Go), github.com/traefik/traefik/v2 (Go), github.com/containous/traefik (Go), github.com/containous/traefik/v2 (Go), github.com/traefik/traefik/v2 (Go), github.com/containous/traefik/v2 (Go), github.com/traefik/traefik/api (Go), github.com/traefik/traefik/v2/pkg/api (Go), and 4 more. Ecosystems affected: Go.

How do I fix CVE-2020-15129?

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 CVE-2020-15129 is resolved across your whole dependency graph.

How do I detect CVE-2020-15129 in my Go dependencies?

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.

How do I mitigate CVE-2020-15129 if there is no patch (or I can't update yet)?

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 does O3 Security protect against CVE-2020-15129?

O3 pinpoints whether CVE-2020-15129 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2020-15129 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-15129 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-15129?

CVE-2020-15129 has an EPSS (Exploit Prediction Scoring System) score of 8.2%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-15129?

CVE-2020-15129 is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2020-15129?

A Nuclei detection template exists for CVE-2020-15129, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-15129 published, and has it been updated?

CVE-2020-15129 was published on July 30, 2020 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2020-15129: traefik Information Disclosure (Medium 4.7)

EPSS Exploitation Probability

via FIRST.org ↗

8.2%probability of exploitation in next 30 days

Lower Risk94th percentile-68.64%

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

12 pkgs affected

🐹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 more

Real-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

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.

Affected Packages

12 total 12 fixed

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 dependency

Detect
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 CVE-2020-15129 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 CVE-2020-15129 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 CVE-2020-15129. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 t

O3 Security · Impact-Aware SCA

Is CVE-2020-15129 in your dependencies?

O3 detects CVE-2020-15129 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

CVE-2020-15129