Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 6 February 2026.
- Which products and versions are affected?
- keylime (PyPI) ECOSYSTEM:introduced=7.12.0,fixed=7.12.2.
- Is there a fix for This vulnerability?
- Yes. keylime (PyPI): upgrade to 7.12.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run keylime (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- keylime (PyPI): upgrade to 7.12.2 or later
pip install "keylime>=7.12.2"
Technical details
A flaw in the Keylime registrar (versions 7.12.0–7.13.0) fails to enforce mandatory client-side TLS authentication, allowing unauthenticated clients with network access to bypass authentication controls. The vulnerability stems from missing validation of client certificates during TLS handshake in the registrar service. An attacker can connect to the registrar endpoint over the network without presenting a valid client certificate and invoke privileged REST API endpoints to list agents, retrieve TPM public data, and delete agents from the system. The vulnerability was introduced in version 7.12.0 and fixed in 7.12.2 and 7.13.1. This is a critical authentication bypass affecting the core trust model of the attestation system.
Affected products
- Keylime Project Keylime 7.12.0 through 7.12.1, 7.13.0
Timeline
- 2026-02-06: disclosed
- 2026-02-09: patched: Fixed in versions 7.12.2 and 7.13.1