CVE-2020-29565 is a medium-severity (CVSS 6.1) Open Redirect vulnerability in horizon. 1 public exploit reference exists, so weaponization risk is real. A fix is available for horizon — see the affected versions and patch details below.
OpenStack Horizon Open redirect in workflow forms
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.
How urgent is this, really
CVE-2020-29565 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
horizon🐍horizon🐍horizon🐍horizonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered in OpenStack Horizon before 15.3.2, 16.x before 16.2.1, 17.x and 18.x before 18.3.3, 18.4.x, and 18.5.x. There is a lack of validation of the "next" parameter, which would allow someone to supply a malicious URL in Horizon that can cause an automatic redirect to the provided malicious URL.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | horizon | all versions | 15.3.2pip install --upgrade 'horizon==15.3.2' |
| 🐍PyPI | horizon | ≥ 16.0.0&&< 16.2.1 | 16.2.1pip install --upgrade 'horizon==16.2.1' |
| 🐍PyPI | horizon | ≥ 17.0.0&&< 18.3.3 | 18.3.3pip install --upgrade 'horizon==18.3.3' |
| 🐍PyPI | horizon | ≥ 18.4.0&&< 18.6.0 | 18.6.0pip install --upgrade 'horizon==18.6.0' |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for horizon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update horizon to 15.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-29565 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2020-29565 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2020-29565. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenStack Platform 13.0 (Queens) | python-django-horizon-1:13.0.3-7.el7ost | RHSA-2020:5572 |
| Red Hat OpenStack Platform 16.1 | python-django-horizon-1:16.2.1-1.20201114033610.el8ost | RHSA-2020:5411 |
Frequently Asked Questions
Is CVE-2020-29565 in your dependencies?
O3 Security finds CVE-2020-29565 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.