Keylime vulnerabilities
We track 5 vulnerabilities in Keylime products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on February 6, 2026.
Latest Keylime vulnerabilities
- 9.8 Critical severity
Red Hat Enterprise Linux 10: Key Exchange without Entity Authentication
A flaw was found in Keylime. The Keylime registrar, since version 7.12.0, does not enforce client-side Transport Layer Security (TLS) authentication. This authentication bypass vulnerability allows unauthenticated clients with network access to perform adminis
- 7.5 High severity
Red Hat Enterprise Linux 9: Excessive Iteration
A flaw was found in Keylime. Due to their blocking nature, the Keylime registrar is subject to a remote denial of service against its SSL connections. This flaw allows an attacker to exhaust all available connections.
- 7.5 High severity
keylime: Exposure of Resource to Wrong Sphere
In Keylime before 6.3.0, Revocation Notifier uses a fixed /tmp path for UNIX domain socket which can allow unprivileged users a method to prohibit keylime operations.
- 7.5 High severity
keylime: Exposure of Sensitive Information to an Unauthorized Actor
A flaw was found in Keylime before 6.3.0. The logic in the Keylime agent for checking for a secure mount can be fooled by previously created unprivileged mounts allowing secrets to be leaked to other processes on the host.
- 9.1 Critical severity
Keylime does not enforce that the agent registrar data is the same when the tenant uses it for…
Keylime does not enforce that the agent registrar data is the same when the tenant uses it for validation of the EK and identity quote and the verifier for validating the integrity quote. This allows an attacker to use one AK, EK pair from a real TPM to pass E