VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

keystone: vulnerability history, versions and safety

keystone is a package in the PyPI ecosystem. Vulert records 88 vulnerabilities for it across 69 releases, from Jul 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
88 vulnerabilities recorded C1 H19 M19 L4 U45
i
6 with no fix published

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

See the unfixed vulnerabilities →
i
31 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 keystone vulnerabilities

Vulert verdict on keystone 30.0.0 i

Updated on 22 Oct 2026

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

Package health score 39/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • 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 30.0.0 — affected i
  • Vulnerabilities on record 88 over 13 years · 31 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 6 i
  • Depended on by 4 packages i
  • Last release this month 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 keystone, 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
30.0.0 30 Sep 2026 C1 H4 M1 U6 Apache-2.0 No Details →
30.0.0.0rc1 15 Sep 2026 C1 H4 M1 U6 Apache-2.0 No Details →
29.1.0 03 Sep 2026 C1 H4 M1 U6 Apache-2.0 No Details →
28.1.0 03 Sep 2026 C1 H4 M1 U6 non-standard No Details →
27.1.0 03 Sep 2026 C1 H5 M1 U7 non-standard No Details →
29.0.2 02 Jul 2026 U1 Apache-2.0 Yes Details →
28.0.2 02 Jul 2026 U1 non-standard Yes Details →
27.0.2 02 Jul 2026 U2 non-standard Yes Details →
29.0.1 16 Apr 2026 H1 U6 Apache-2.0 No Details →
26.1.1 16 Apr 2026 H1 M4 U7 non-standard No Details →
28.0.1 16 Apr 2026 H1 U6 non-standard No Details →
27.0.1 16 Apr 2026 H1 M4 U7 non-standard No Details →
29.0.0 01 Apr 2026 H1 U6 Apache-2.0 No Details →
29.0.0.0rc1 16 Mar 2026 H1 U1 Apache-2.0 No Details →
26.1.0 26 Jan 2026 H2 M4 L1 U8 non-standard No Details →
28.0.0 01 Oct 2025 H2 U7 Apache-2.0 No Details →
28.0.0.0rc1 11 Sep 2025 H2 U3 Apache-2.0 No Details →
27.0.0 02 Apr 2025 H2 M4 U7 Apache-2.0 No Details →
27.0.0.0rc1 13 Mar 2025 H2 M4 U8 Apache-2.0 No Details →
24.1.0 28 Feb 2025 H3 M4 L1 U9 Apache-2.0 No Details →
26.0.0 02 Oct 2024 H3 M5 L1 U12 non-standard No Details →
26.0.0.0rc1 12 Sep 2024 H4 M5 L1 U12 non-standard No Details →
23.0.2 06 Sep 2024 H4 M5 L1 U12 non-standard No Details →
22.0.2 04 Apr 2024 H4 M5 L1 U12 non-standard No Details →
25.0.0 03 Apr 2024 H4 M5 L1 U12 non-standard No Details →
25.0.0.0rc1 19 Mar 2024 H4 M5 L1 U12 non-standard No Details →
21.0.1 09 Oct 2023 H4 M5 L1 U14 non-standard No Details →
23.0.1 09 Oct 2023 H4 M5 L1 U14 non-standard No Details →
22.0.1 09 Oct 2023 H4 M5 L1 U14 non-standard No Details →
24.0.0 04 Oct 2023 H4 M5 L1 U14 non-standard No Details →
24.0.0.0rc1 14 Sep 2023 H4 M5 L1 U14 non-standard No Details →
23.0.0 22 Mar 2023 H5 M5 L1 U14 non-standard No Details →
23.0.0.0rc1 07 Mar 2023 H5 M5 L1 U14 non-standard No Details →
20.0.1 18 Jan 2023 C1 H5 M5 L1 U15 non-standard No Details →
22.0.0 05 Oct 2022 H5 M5 L1 U14 non-standard No Details →
22.0.0.0rc1 14 Sep 2022 H5 M5 L1 U14 non-standard No Details →
19.0.1 18 Aug 2022 C1 H5 M5 L1 U15 non-standard No Details →
21.0.0 30 Mar 2022 C1 H5 M5 L1 U15 non-standard No Details →
21.0.0.0rc1 11 Mar 2022 C1 H5 M5 L1 U15 non-standard No Details →
18.1.0 31 Jan 2022 C1 H5 M5 L1 U15 non-standard No Details →
20.0.0 06 Oct 2021 C1 H5 M5 L1 U15 non-standard No Details →
20.0.0.0rc1 17 Sep 2021 C1 H5 M5 L1 U15 non-standard No Details →
17.0.1 01 Sep 2021 C1 H5 M5 L1 U15 non-standard No Details →
16.0.2 07 Jun 2021 C1 H5 M5 L1 U15 non-standard No Details →
19.0.0 14 Apr 2021 C1 H5 M5 L1 U16 non-standard No Details →
19.0.0.0rc2 09 Apr 2021 C1 H5 M5 L1 U15 non-standard No Details →
19.0.0.0rc1 26 Mar 2021 C1 H5 M5 L1 U15 non-standard No Details →
18.0.0 14 Oct 2020 C1 H5 M5 L1 U16 non-standard No Details →
18.0.0.0rc1 25 Sep 2020 C1 H5 M5 L1 U15 non-standard No Details →
17.0.0 13 May 2020 C1 H5 M5 L1 U16 non-standard No Details →
16.0.1 12 May 2020 C1 H6 M5 L1 U16 non-standard No Details →
15.0.1 12 May 2020 C1 H6 M5 L1 U18 non-standard No Details →
17.0.0.0rc2 08 May 2020 C1 H5 M5 L1 U15 non-standard No Details →
17.0.0.0rc1 24 Apr 2020 C1 H5 M5 L1 U15 non-standard No Details →
14.2.0 24 Feb 2020 C1 H8 M5 L1 U22 non-standard No Details →
13.0.4 31 Oct 2019 C1 H8 M1 U17 non-standard No Details →
13.0.3 30 Oct 2019 C1 H8 M1 U17 non-standard No Details →
16.0.0 16 Oct 2019 C1 H6 M5 L1 U18 non-standard No Details →
16.0.0.0rc2 10 Oct 2019 C1 H6 M6 L1 U18 non-standard No Details →
16.0.0.0rc1 27 Sep 2019 C1 H6 M6 L1 U18 non-standard No Details →
12.0.3 17 Apr 2019 C1 H7 M1 U17 non-standard No Details →
15.0.0 10 Apr 2019 C1 H10 M5 L1 U22 non-standard No Details →
14.1.0 04 Apr 2019 C1 H8 M5 L1 U22 non-standard No Details →
15.0.0.0rc2 03 Apr 2019 C1 H8 M5 L1 U22 non-standard No Details →
15.0.0.0rc1 21 Mar 2019 C1 H8 M5 L1 U22 non-standard No Details →
14.0.1 01 Nov 2018 C1 H8 M5 L1 U23 non-standard No Details →
12.0.2 31 Oct 2018 C1 H7 M1 U17 non-standard No Details →
13.0.2 31 Oct 2018 C1 H8 M1 U17 non-standard No Details →
14.0.0 08 Oct 2018 C1 H8 M5 L1 U23 non-standard No Details →

All 69 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 4
  • 2013 4
  • 2014 5
  • 2016 1
  • 2018 2
  • 2019 2
  • 2020 4
  • 2021 1
  • 2022 34
  • 2025 1
  • 2026 30

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

03 Vulnerabilities

Recorded vulnerabilities for keystone

The 5 most severe of 88 vulnerabilities recorded for this package

Search all 88 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-3563: Keystone Application Secret Verification Bypass Vulnerability 9.1 critical No fix published 29 Jun 2026
CVE-2021-3563: Openstack Keystone Incorrect Authorization vulnerability 9.1 critical No fix published 27 Aug 2022
CVE-2020-12691: OpenStack Keystone V3 /credentials endpoint policy logic allows to change credentials owner or target project ID 8.8 high 15.0.1 24 May 2022
CVE-2019-19687: OpenStack Keystone Credential Leakage 8.8 high No fix published 24 May 2022
OpenStack Keystone EC2 Credential Escalation 8.8 high 15.0.1 24 May 2022

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 keystone

Is keystone safe to use?

Vulert records 88 vulnerabilities for keystone in PyPI: 1 critical, 19 high, 19 medium and 4 low, plus 45 not yet rated. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is keystone's Vulert package health score?

Vulert scores keystone 39/100, which reads as risky. 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 keystone affected?

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

Which version of keystone should I use?

30.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 keystone have?

88 vulnerabilities are recorded for keystone in the PyPI ecosystem: 1 critical, 19 high, 19 medium and 4 low, plus 45 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 keystone vulnerabilities disclosed?

31 vulnerabilities were recorded for keystone in the last 12 months, and the oldest entry in this database dates to 31 Jul 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 keystone 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 keystone for upcoming vulnerabilities?

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