Skip to main content
No exploitation reportedFix available

CVE-2020-15129

No exploitation reported by the sources we read.

  • Published2020-07-30
  • Fixed in2.3.0-rc3 · 2.2.8 · 1.7.26
  • WeaknessCWE-601

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2020-07-3016:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-15129?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-15129?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV · NVD
Traefik
BranchAffectedFixed in
2.3≥ 2.3.0-rc1, < 2.3.0-rc32.3.0-rc3
2.2≥ 2.2.0, < 2.2.82.2.8
2.2< 2.2.82.2.8
1.7< 1.7.261.7.26
1.x≥ 1.5.0-rc5, < 1.7.261.7.26
2.3= 2.3.0no fix published
traefik/traefik
BranchAffectedFixed in
2.3< 2.3.0-rc62.3.0-rc6
2.3≥ 2.3.0-rc1, < 2.3.0-rc62.3.0-rc6
traefik/traefik/v2/pkg/api
BranchAffectedFixed in
2.3< 2.3.0-rc62.3.0-rc6
2.3≥ 2.3.0-rc1, < 2.3.0-rc62.3.0-rc6

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Traefik to 2.3.0-rc3 · 2.2.8 · 1.7.26

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CNACVSS 3.16.1read 2026-10-23
  • NVDCVSS 3.14.7read 2026-10-23
  • NVDCVSS 2.04read 2026-10-23
  • CNAweakness (CWE)CWE-601read 2026-10-23
  • NVDweakness (CWE)CWE-601read 2026-10-23
  • FIRST EPSSEPSS score8.0 %2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N
Published
2020-07-30
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2020-15129?

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.

Is CVE-2020-15129 actively exploited?

Active exploitation of CVE-2020-15129 has not been confirmed. Its EPSS score was 8.0% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

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

CVE-2020-15129 has a CVSS v3 base score of 4.7 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N.

Running traefik/traefik? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month