VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

keystonemiddleware: vulnerability history, versions and safety

keystonemiddleware is a package in the PyPI ecosystem. Vulert records 5 vulnerabilities for it across 20 releases, from Oct 2014 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H2 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all keystonemiddleware vulnerabilities

Vulert verdict on keystonemiddleware 13.0.1 i

Updated on 23 Oct 2026

Good news: 13.0.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 89/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Not enough data

What to do: Stay on 13.0.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 13.0.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 13.0.1 — unaffected i
  • Vulnerabilities on record 5 over 7 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 109 packages i
  • Last release 1 month ago i
  • Licence non-standard 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 keystonemiddleware, 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
13.0.1 25 Aug 2026 none non-standard — Details →
13.0.0 13 May 2026 none non-standard — Details →
10.7.2 13 Apr 2026 none non-standard — Details →
10.9.1 23 Mar 2026 none non-standard — Details →
12.0.0 17 Feb 2026 none non-standard — Details →
10.12.1 19 Jan 2026 none non-standard — Details →
11.0.0 19 Jan 2026 none non-standard — Details →
10.12.0 21 Aug 2025 none Apache-2.0 — Details →
10.11.0 07 Jul 2025 none Apache-2.0 — Details →
10.10.0 16 May 2025 none Apache-2.0 — Details →
10.9.0 21 Feb 2025 none Apache-2.0 — Details →
10.8.0 21 Nov 2024 none non-standard — Details →
10.7.1 30 Aug 2024 none non-standard — Details →
10.7.0 23 May 2024 none non-standard — Details →
10.6.0 23 Feb 2024 none non-standard — Details →
10.1.1 08 Feb 2024 none non-standard — Details →
10.5.0 20 Nov 2023 none non-standard — Details →
10.4.1 29 Aug 2023 none non-standard — Details →
10.4.0 07 Jul 2023 none non-standard — Details →
10.3.0 17 May 2023 none non-standard — Details →
10.2.0 06 Jan 2023 none non-standard — Details →
10.1.0 30 Aug 2022 none non-standard — Details →
10.0.1 26 Aug 2022 none non-standard — Details →
10.0.0 15 Jul 2022 none non-standard — Details →
9.5.0 20 May 2022 none non-standard — Details →
9.4.0 16 Feb 2022 none non-standard — Details →
9.3.0 01 Jun 2021 none non-standard — Details →
9.2.0 02 Dec 2020 none non-standard — Details →
9.1.0 03 Aug 2020 none non-standard — Details →
9.0.0 02 Apr 2020 none non-standard — Details →
6.0.1 20 Mar 2020 none non-standard — Details →
5.2.2 24 Feb 2020 none non-standard — Details →
8.0.0 06 Jan 2020 none non-standard — Details →
4.22.0 30 Oct 2019 none non-standard — Details →
7.0.1 06 Sep 2019 none non-standard — Details →
5.2.1 12 Aug 2019 none non-standard — Details →
7.0.0 22 Jul 2019 none non-standard — Details →
6.1.0 14 Jun 2019 none non-standard — Details →
4.17.1 17 Apr 2019 none non-standard — Details →
6.0.0 28 Feb 2019 none non-standard — Details →
5.3.0 24 Oct 2018 none non-standard — Details →
5.2.0 20 Jul 2018 none non-standard — Details →
5.1.0 09 May 2018 none non-standard — Details →
5.0.0 19 Apr 2018 none non-standard — Details →
4.21.0 09 Jan 2018 none non-standard — Details →
4.20.0 28 Dec 2017 none non-standard — Details →
4.19.0 08 Dec 2017 none non-standard — Details →
4.18.0 15 Nov 2017 none non-standard — Details →
4.17.0 20 Jul 2017 none non-standard — Details →
4.16.0 05 Jun 2017 none non-standard — Details →
4.15.0 06 Apr 2017 none non-standard — Details →
4.9.1 01 Feb 2017 none non-standard — Details →
4.14.0 18 Jan 2017 none non-standard — Details →
4.13.1 03 Jan 2017 none non-standard — Details →
4.13.0 02 Jan 2017 none non-standard — Details →
4.12.0 15 Dec 2016 none non-standard — Details →
4.11.0 01 Dec 2016 none non-standard — Details →
2.3.4 10 Nov 2016 none non-standard — Details →
4.10.0 10 Oct 2016 none non-standard — Details →
4.9.0 23 Aug 2016 none non-standard — Details →
4.8.0 03 Aug 2016 none non-standard — Details →
4.7.0 28 Jul 2016 none non-standard — Details →
4.6.0 05 Jul 2016 none non-standard — Details →
4.4.1 23 May 2016 none non-standard — Details →
4.5.1 23 May 2016 none non-standard — Details →
4.5.0 19 May 2016 none non-standard — Details →
4.4.0 25 Mar 2016 none non-standard — Details →
2.3.3 03 Mar 2016 none non-standard — Details →
4.3.0 17 Feb 2016 none non-standard — Details →
4.2.0 25 Jan 2016 none non-standard — Details →
4.1.0 13 Jan 2016 none non-standard — Details →
4.0.0 01 Dec 2015 none non-standard — Details →
2.3.2 24 Nov 2015 U1 non-standard Yes Details →
1.5.3 23 Nov 2015 H1 U2 non-standard Yes Details →
3.0.0 04 Nov 2015 none non-standard — Details →
2.4.1 14 Oct 2015 none non-standard — Details →
2.4.0 13 Oct 2015 none non-standard — Details →
2.3.1 06 Oct 2015 U1 non-standard Yes Details →
2.3.0 18 Sep 2015 U1 non-standard Yes Details →
2.2.0 03 Sep 2015 U1 non-standard Yes Details →
2.1.0 07 Jul 2015 U1 non-standard Yes Details →
1.5.2 29 Jun 2015 H1 U2 non-standard Yes Details →
2.0.0 17 Jun 2015 U1 non-standard Yes Details →
1.3.2 26 May 2015 H1 U2 non-standard Yes Details →
1.6.1 30 Apr 2015 U1 non-standard Yes Details →
1.5.1 27 Apr 2015 H1 U2 non-standard Yes Details →
1.6.0 21 Apr 2015 U1 non-standard Yes Details →
1.5.0 11 Mar 2015 H1 U2 non-standard Yes Details →
1.4.0 10 Feb 2015 H1 U2 non-standard Yes Details →
1.3.1 22 Dec 2014 H1 U2 non-standard Yes Details →
1.3.0 18 Dec 2014 H1 U2 non-standard Yes Details →
1.2.0 25 Sep 2014 H1 U2 non-standard Yes Details →
1.1.1 21 Aug 2014 H1 U3 non-standard Yes Details →
1.1.0 04 Aug 2014 H1 U3 non-standard Yes Details →
1.0.0 03 Jul 2014 H1 U3 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 1
  • 2015 1
  • 2016 1
  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for keystonemiddleware

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-1852: OpenStack keystonemiddleware and python-keystoneclient Man-in-the-Middle Vulnerability 7.5 high 1.6.0 17 May 2022
CVE-2014-7144: OpenStack keystonemiddleware Certificate Verification Bypass 5.9 high 0.11.0 17 May 2022
CVE-2015-7546: OpenStack Keystone Identity Service Token Bypass N/A unrated 1.5.4 03 Feb 2016
CVE-2014-7144: OpenStack keystonemiddleware Insecure Certificate Verification N/A unrated 0.11.0 02 Oct 2014
CVE-2015-1852: OpenStack keystonemiddleware s3_token Middleware Insecure Certificate Verification N/A unrated 1.6.0 17 Apr 2015

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 keystonemiddleware

Is keystonemiddleware safe to use?

Vulert records 5 vulnerabilities for keystonemiddleware in PyPI: 0 critical, 2 high, 0 medium and 0 low, plus 3 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is keystonemiddleware's Vulert package health score?

Vulert scores keystonemiddleware 89/100, which reads as healthy. 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).

Is the latest version of keystonemiddleware affected?

No. 13.0.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of keystonemiddleware should I use?

13.0.1 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 keystonemiddleware have?

5 vulnerabilities are recorded for keystonemiddleware in the PyPI ecosystem: 0 critical, 2 high, 0 medium and 0 low, plus 3 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 keystonemiddleware vulnerabilities disclosed?

0 vulnerabilities were recorded for keystonemiddleware in the last 12 months, and the oldest entry in this database dates to 02 Oct 2014. 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 keystonemiddleware 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 keystonemiddleware for upcoming vulnerabilities?

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