VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

keylime: vulnerability history, versions and safety

keylime is a package in the PyPI ecosystem. Vulert records 21 vulnerabilities for it across 31 releases, from May 2022 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
21 vulnerabilities recorded C3 H5 M4 U9
i
1 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 keylime vulnerabilities

Vulert verdict on keylime 7.14.3 i

Updated on 23 Oct 2026

Careful: 7.14.3 has 3 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 55/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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 7.14.3 — affected i
  • Vulnerabilities on record 21 over 4 years · 10 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Stars 569 i
  • OpenSSF scorecard 6/10 i
  • Last release 3 months 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 keylime, 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
7.14.3 06 Jul 2026 U3 Apache-2.0 No Details →
7.14.2 06 May 2026 U3 Apache-2.0 No Details →
7.14.1 12 Feb 2026 M2 U1 Apache-2.0 Yes Details →
7.14.0 06 Feb 2026 M2 U1 Apache-2.0 Yes Details →
7.13.1 06 Feb 2026 U3 Apache-2.0 No Details →
7.12.2 06 Feb 2026 H1 U3 Apache-2.0 No Details →
7.13.0 15 Sep 2025 U3 Apache-2.0 No Details →
7.12.1 14 Feb 2025 C2 H1 Apache-2.0 Yes Details →
7.12.0 21 Jan 2025 C2 H1 M1 U1 Apache-2.0 Yes Details →
7.10.0 13 Mar 2024 H1 U1 Apache-2.0 Yes Details →
7.9.0 30 Jan 2024 H1 U1 Apache-2.0 Yes Details →
7.8.0 04 Dec 2023 H1 U1 Apache-2.0 Yes Details →
7.7.0 31 Oct 2023 H1 U1 Apache-2.0 Yes Details →
7.6.0 30 Sep 2023 H1 U1 Apache-2.0 Yes Details →
7.5.0 23 Aug 2023 H1 U1 Apache-2.0 Yes Details →
7.4.0 01 Aug 2023 H2 U2 Apache-2.0 Yes Details →
7.3.0 30 Jun 2023 H4 U3 Apache-2.0 Yes Details →
7.2.5 02 Jun 2023 H4 U3 Apache-2.0 Yes Details →
7.0.0 25 Apr 2023 H4 M1 U4 Apache-2.0 Yes Details →
6.8.0 25 Apr 2023 H4 M1 U4 Apache-2.0 Yes Details →
6.6.0 02 Feb 2023 H4 M1 U4 Apache-2.0 Yes Details →
6.5.3 20 Jan 2023 H4 M1 U4 Apache-2.0 Yes Details →
6.5.2 10 Nov 2022 H4 M1 U4 Apache-2.0 Yes Details →
6.5.1 11 Oct 2022 H4 M1 U4 Apache-2.0 Yes Details →
6.5.0 21 Sep 2022 H5 M1 U5 Apache-2.0 Yes Details →
6.4.3 24 Aug 2022 H5 M1 U5 Apache-2.0 Yes Details →
6.4.2 07 Jul 2022 H5 M1 U5 Apache-2.0 Yes Details →
6.4.1 06 Jun 2022 H5 M1 U5 Apache-2.0 Yes Details →
6.4.0 04 May 2022 H5 M1 U5 Apache-2.0 Yes Details →
6.3.2 06 Apr 2022 C1 H5 M1 U6 Apache-2.0 Yes Details →
6.3.1 14 Feb 2022 C1 H5 M1 U6 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4
  • 2023 6
  • 2025 3
  • 2026 8

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

03 Vulnerabilities

Recorded vulnerabilities for keylime

The 5 most severe of 21 vulnerabilities recorded for this package

Search all 21 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-1709: Keylime Package TLS Authentication Bypass Vulnerability 9.8 critical 7.12.0 06 Feb 2026
CVE-2026-1709: Keylime Critical Authentication Bypass Vulnerability 9.4 critical 7.12.2 06 Feb 2026
Critical Authentication Bypass in Keylime Package 9.4 critical 7.12.2 06 Feb 2026
CVE-2022-1053: keylime - Tenant and Verifier Data Mismatch 9.1 critical 6.4.0 05 May 2022
CVE-2025-13609: Keylime Package Vulnerability Allows Agent Impersonation 8.2 high No fix published 24 Nov 2025

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 keylime

Is keylime safe to use?

Vulert records 21 vulnerabilities for keylime in PyPI: 3 critical, 5 high, 4 medium and 0 low, plus 9 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is keylime's Vulert package health score?

Vulert scores keylime 55/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 keylime affected?

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

Which version of keylime should I use?

7.14.3 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 keylime have?

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

10 vulnerabilities were recorded for keylime in the last 12 months, and the oldest entry in this database dates to 05 May 2022. 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 keylime 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 keylime for upcoming vulnerabilities?

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