VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

horizon: vulnerability history, versions and safety

horizon is a package in the PyPI ecosystem. Vulert records 27 vulnerabilities for it across 108 releases, from Jun 2012 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
27 vulnerabilities recorded M11 L2 U14
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
10 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all horizon vulnerabilities

Vulert verdict on horizon 27.0.0 i

Updated on 23 Oct 2026

Careful: 27.0.0 has 4 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 56/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 27.0.0 — affected i
  • Vulnerabilities on record 27 over 14 years · 10 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 6.1 i
  • With no published fix 2 i
  • Depended on by 34 packages i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for horizon, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
27.0.0 18 Sep 2026 M1 U3 Apache-2.0 No Details →
26.0.0 03 Jul 2026 M1 U3 Apache-2.0 No Details →
25.7.3 05 May 2026 M1 U1 non-standard No Details →
25.7.2 27 Apr 2026 M2 U2 non-standard No Details →
25.7.1 27 Mar 2026 M2 U2 non-standard No Details →
25.5.2 19 Mar 2026 M1 U1 non-standard No Details →
25.3.2 19 Mar 2026 M1 U1 non-standard No Details →
25.1.2 19 Mar 2026 M1 U1 non-standard No Details →
25.7.0 13 Mar 2026 M2 U2 non-standard No Details →
25.6.0 10 Mar 2026 M2 U2 non-standard No Details →
25.5.1 19 Sep 2025 M1 U1 Apache-2.0 No Details →
25.5.0 11 Sep 2025 M1 U1 Apache-2.0 No Details →
24.0.2 04 Sep 2025 M1 U1 Apache-2.0 No Details →
25.1.1 04 Sep 2025 M1 U1 Apache-2.0 No Details →
25.3.1 04 Sep 2025 M1 U1 Apache-2.0 No Details →
24.0.1 05 Jun 2025 M1 U1 Apache-2.0 No Details →
25.4.0 28 May 2025 M1 U1 Apache-2.0 No Details →
23.3.1 30 Apr 2025 M1 U1 Apache-2.0 No Details →
25.3.0 19 Mar 2025 M1 U1 Apache-2.0 No Details →
25.2.0 27 Feb 2025 M1 U1 Apache-2.0 No Details →
25.1.0 16 Sep 2024 M1 U3 non-standard No Details →
23.1.1 01 Aug 2024 M1 U3 non-standard No Details →
25.0.0 26 Jul 2024 M1 U3 non-standard No Details →
23.0.2 30 Apr 2024 M1 U3 non-standard No Details →
24.0.0 18 Mar 2024 M1 U3 non-standard No Details →
23.0.1 05 Mar 2024 M1 U3 non-standard No Details →
23.4.0 15 Jan 2024 M1 U3 non-standard No Details →
23.3.0 22 Sep 2023 M1 U4 non-standard No Details →
22.1.1 01 Aug 2023 M1 U4 non-standard No Details →
23.2.0 11 Jul 2023 M1 U4 non-standard No Details →
20.1.4 13 Apr 2023 M2 U5 non-standard No Details →
23.1.0 07 Mar 2023 M1 U4 non-standard No Details →
20.1.3 18 Jan 2023 M2 U5 non-standard No Details →
19.4.0 04 Nov 2022 M2 U5 non-standard No Details →
23.0.0 20 Sep 2022 M1 U4 non-standard No Details →
19.3.0 30 Jun 2022 M1 U4 non-standard No Details →
22.2.0 23 Jun 2022 M1 U4 non-standard No Details →
20.1.2 29 Apr 2022 M2 U5 non-standard No Details →
18.6.4 19 Apr 2022 M1 U4 non-standard No Details →
22.1.0 29 Mar 2022 M1 U4 non-standard No Details →
22.0.0 23 Mar 2022 M1 U4 non-standard No Details →
20.1.1 03 Feb 2022 M2 U5 non-standard No Details →
21.0.0 26 Jan 2022 M1 U4 non-standard No Details →
18.6.3 26 Jan 2022 M1 U4 non-standard No Details →
18.3.5 26 Nov 2021 M1 U4 non-standard No Details →
20.2.0 27 Oct 2021 M1 U4 non-standard No Details →
20.1.0 23 Sep 2021 M2 U5 non-standard No Details →
18.3.4 03 Aug 2021 M1 U4 non-standard No Details →
20.0.0 29 Jul 2021 M2 U5 non-standard No Details →
16.2.2 17 May 2021 M1 U4 non-standard No Details →
19.2.0 12 Apr 2021 M1 U4 non-standard No Details →
19.1.0 15 Mar 2021 M1 U4 non-standard No Details →
18.6.2 16 Feb 2021 M1 U4 non-standard No Details →
18.3.3 16 Feb 2021 M1 U4 non-standard No Details →
16.2.1 04 Feb 2021 M1 U4 non-standard No Details →
19.0.0 05 Dec 2020 M1 U4 non-standard No Details →
15.3.2 12 Nov 2020 M1 U4 non-standard No Details →
18.6.1 09 Oct 2020 M1 U4 non-standard No Details →
18.6.0 25 Sep 2020 M1 U4 non-standard No Details →
18.5.0 10 Sep 2020 M1 U5 non-standard No Details →
15.3.1 20 Jul 2020 M2 U5 non-standard No Details →
18.4.1 22 Jun 2020 M1 U5 non-standard No Details →
18.4.0 18 Jun 2020 M1 U5 non-standard No Details →
16.2.0 11 Jun 2020 M1 U5 non-standard No Details →
18.3.2 07 May 2020 M1 U5 non-standard No Details →
15.3.0 30 Apr 2020 M2 U5 non-standard No Details →
18.3.1 20 Apr 2020 M1 U5 non-standard No Details →
18.3.0 17 Apr 2020 M1 U5 non-standard No Details →
18.2.0 25 Mar 2020 M1 U5 non-standard No Details →
18.1.0 23 Mar 2020 M1 U5 non-standard No Details →
14.1.0 23 Jan 2020 M2 U4 non-standard No Details →
15.2.0 23 Jan 2020 M2 U4 non-standard No Details →
16.1.0 23 Jan 2020 M1 U5 non-standard No Details →
18.0.0 09 Jan 2020 M1 U5 non-standard No Details →
17.1.0 16 Dec 2019 M1 U5 non-standard No Details →
17.0.0 21 Nov 2019 M1 U5 non-standard No Details →
15.1.1 22 Oct 2019 M2 U4 non-standard No Details →
14.0.4 22 Oct 2019 M2 U4 non-standard No Details →
13.0.3 22 Oct 2019 M2 U4 non-standard No Details →
16.0.0 16 Oct 2019 M1 U5 non-standard No Details →
16.0.0.0rc2 10 Oct 2019 M1 U4 non-standard No Details →
16.0.0.0rc1 27 Sep 2019 M1 U4 non-standard No Details →
16.0.0.0b2 13 Sep 2019 M1 U4 non-standard No Details →
16.0.0.0b1 12 Jun 2019 M1 U4 non-standard No Details →
15.1.0 28 May 2019 M2 U4 non-standard No Details →
14.0.3 10 May 2019 M2 U4 non-standard No Details →
13.0.2 09 May 2019 M2 U4 non-standard No Details →
12.0.4 26 Apr 2019 M2 U4 non-standard No Details →
15.0.0 10 Apr 2019 M2 U4 non-standard No Details →
15.0.0.0rc2 04 Apr 2019 M2 U4 non-standard No Details →
15.0.0.0rc1 21 Mar 2019 M2 U4 non-standard No Details →
15.0.0.0b2 07 Mar 2019 M2 U4 non-standard No Details →
14.0.2 03 Dec 2018 M2 U4 non-standard No Details →
15.0.0.0b1 25 Oct 2018 M2 U4 non-standard No Details →
14.0.1 22 Oct 2018 M2 U4 non-standard No Details →
14.0.0 30 Aug 2018 M2 U4 non-standard No Details →
14.0.0.0rc2 22 Aug 2018 M2 U4 non-standard No Details →
14.0.0.0rc1 09 Aug 2018 M2 U4 non-standard No Details →
14.0.0.0b3 26 Jul 2018 M2 U4 non-standard No Details →
14.0.0.0b2 07 Jun 2018 M2 U4 non-standard No Details →
13.0.1 08 May 2018 M2 U4 — No Details →
12.0.3 08 May 2018 M2 U4 — No Details →
14.0.0.0b1 19 Apr 2018 M2 U4 — No Details →
13.0.0 28 Feb 2018 M2 U4 — No Details →
13.0.0.0rc2 21 Feb 2018 M2 U4 — No Details →
13.0.0.0rc1 09 Feb 2018 M2 U4 — No Details →
13.0.0.0b3 26 Jan 2018 M2 U4 — No Details →
12.0.2 16 Jan 2018 M2 U4 — No Details →

All 108 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2012 3
  • 2015 1
  • 2020 1
  • 2022 10
  • 2023 2
  • 2026 10

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 10 of the 27 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for horizon

The 5 most severe of 27 vulnerabilities recorded for this package

Search all 27 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
OpenStack Horizon Open Redirect in Workflow Forms 6.1 medium 15.3.2 24 May 2022
CVE-2022-45582: Horizon Web Dashboard Open Redirect vulnerability 6.1 medium 20.2.0 22 Aug 2023
CVE-2022-45582: Horizon Web Dashboard Open Redirect vulnerability 6.1 medium 20.2.0 22 Aug 2023
OpenStack Dashboard (Horizon) Cross-site scripting (XSS) vulnerability in horizon 6.1 medium 8.0.0a0 17 May 2022
CVE-2026-55748: OpenStack Horizon RC File Generation Vulnerability in Project Names 6.0 medium No fix published 13 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About horizon

Is horizon safe to use?

Vulert records 27 vulnerabilities for horizon in PyPI: 0 critical, 0 high, 11 medium and 2 low, plus 14 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is horizon's Vulert package health score?

Vulert scores horizon 56/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of horizon affected?

Yes. 27.0.0, the version you would install today, has 4 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of horizon should I use?

27.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does horizon have?

27 vulnerabilities are recorded for horizon in the PyPI ecosystem: 0 critical, 0 high, 11 medium and 2 low, plus 14 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new horizon vulnerabilities disclosed?

10 vulnerabilities were recorded for horizon in the last 12 months, and the oldest entry in this database dates to 05 Jun 2012. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of horizon are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor horizon for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the horizon version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.