CVE-2021-43310: keylime · CWE-290
Affects keylimeSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 6.3.0 as a priority.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.3.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade keylime/keylime to 6.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubkeylime/keylimepkg:github/keylime/keylimeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate the risks posed by CVE-2021-43310, European organizations should take the following specific actions: 1) Immediately upgrade all Keylime deployments to version 6.3.0 or later, where the vulnerability is patched. 3) Restrict network access to Keylime agents by implementing network segmentation and firewall rules to limit exposure only to trusted management systems. 4) Employ strong authentication and authorization controls around Keylime components, ensuring that only authorized entities can communicate with agents. 5) Monitor logs and network traffic for anomalous requests that could indicate attempts to exploit this vulnerability, focusing on unexpected key reset requests. 6) Integrate vulnerability scanning and patch management processes to promptly identify and remediate Keylime-related vulnerabilities in the future. 7) For organizations using Keylime in critical infrastructure, consider additional compensating controls such as application whitelisting and endpoint detection and response (EDR) solutions to detect and prevent exploitation attempts.
Description
A vulnerability in Keylime before 6.3.0 allows an attacker to craft a request to the agent that resets the U and V keys as if the agent were being re-added to a verifier. This could lead to a remote code execution.