keylime: A vulnerability has been identified in keylime where an attacker can exploit this flaw by registering a new agent usi...
CVE-2025-13609 is fixed in 8 products on 1 platform, first by RHSA-2026:0429, released November 24, 2025. It is not reported as exploited. Patch Radar priority: High.
A vulnerability has been identified in keylime where an attacker can exploit this flaw by registering a new agent using a different Trusted Platform Module (TPM) device but claiming an existing agent's unique identifier (UUID). This action overwrites the legitimate agent's identity, enabling the attacker to impersonate the compromised agent and potentially bypass security controls.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| keylime · RHEL 10 | 7.12.1-2.el10_0.4 | RHSA-2026:0429 | Nov 24, 2025 |
| keylime · RHEL 9 | 0:7.12.1-11.el9_7.3 | RHSA-2025:23210 | Dec 16, 2025 |
| keylime · almalinux 9 | 7.12.1-11.el9_7.3 | ALSA-2025:23210 | Dec 15, 2025 |
| keylime · ol 10 | 0:7.12.1-11.el10_1.3 | ELSA-2025-23201 | Dec 16, 2025 |
| keylime · ol 9 | 0:7.12.1-11.el9_7.3 | ELSA-2025-23210 | Dec 16, 2025 |
| keylime · opensuse-leap 15.6 | 6.3.2-150400.4.23.1 | SUSE-SU-2026:0217-1 | Jan 22, 2026 |
| keylime · opensuse-leap 16.0 | 7.13.0+40-160000.1.1 | OPENSUSE-SU-2025:20159-1 | Dec 12, 2025 |
| keylime · rocky 10 | 0:7.12.1-11.el10_1.3 | RLSA-2025:23201 | Dec 18, 2025 |
| keylime · rocky 9 | 0:7.12.1-11.el9_7.3 | RLSA-2025:23210 | Dec 17, 2025 |
| keylime · sles 15.6 | 6.3.2-150400.4.23.1 | SUSE-SU-2026:0217-1 | Jan 22, 2026 |
| keylime · sles 15.7 | 6.3.2-150400.4.23.1 | SUSE-SU-2026:0217-1 | Jan 22, 2026 |
| keylime · sles 16.0 | 7.13.0+40-160000.1.1 | SUSE-SU-2025:21194-1 | Dec 12, 2025 |
| keylime-base · RHEL 9 | 0:7.12.1-11.el9_7.3 | RHSA-2025:23210 | Dec 16, 2025 |
| keylime-base · almalinux 9 | 7.12.1-11.el9_7.3 | ALSA-2025:23210 | Dec 15, 2025 |
| keylime-base · ol 10 | 0:7.12.1-11.el10_1.3 | ELSA-2025-23201 | Dec 16, 2025 |
| keylime-base · ol 9 | 0:7.12.1-11.el9_7.3 | ELSA-2025-23210 | Dec 16, 2025 |
| keylime-registrar · RHEL 9 | 0:7.12.1-11.el9_7.3 | RHSA-2025:23210 | Dec 16, 2025 |
| keylime-registrar · almalinux 9 | 7.12.1-11.el9_7.3 | ALSA-2025:23210 | Dec 15, 2025 |
| keylime-registrar · ol 10 | 0:7.12.1-11.el10_1.3 | ELSA-2025-23201 | Dec 16, 2025 |
| keylime-registrar · ol 9 | 0:7.12.1-11.el9_7.3 | ELSA-2025-23210 | Dec 16, 2025 |
| keylime-selinux · RHEL 9 | 0:7.12.1-11.el9_7.3 | RHSA-2025:23210 | Dec 16, 2025 |
| keylime-selinux · almalinux 10 | 7.12.1-11.el10_1.3 | ALSA-2025:23201 | Dec 15, 2025 |
| keylime-selinux · almalinux 9 | 7.12.1-11.el9_7.3 | ALSA-2025:23210 | Dec 15, 2025 |
| keylime-selinux · ol 10 | 0:7.12.1-11.el10_1.3 | ELSA-2025-23201 | Dec 16, 2025 |
| keylime-selinux · ol 9 | 0:7.12.1-11.el9_7.3 | ELSA-2025-23210 | Dec 16, 2025 |
| keylime-tenant · RHEL 9 | 0:7.12.1-11.el9_7.3 | RHSA-2025:23210 | Dec 16, 2025 |
| keylime-tenant · almalinux 9 | 7.12.1-11.el9_7.3 | ALSA-2025:23210 | Dec 15, 2025 |
| keylime-tenant · ol 10 | 0:7.12.1-11.el10_1.3 | ELSA-2025-23201 | Dec 16, 2025 |
| keylime-tenant · ol 9 | 0:7.12.1-11.el9_7.3 | ELSA-2025-23210 | Dec 16, 2025 |
| keylime-tools · ol 10 | 0:7.12.1-11.el10_1.3 | ELSA-2025-23201 | Dec 16, 2025 |
| keylime-verifier · RHEL 9 | 0:7.12.1-11.el9_7.3 | RHSA-2025:23210 | Dec 16, 2025 |
| keylime-verifier · almalinux 9 | 7.12.1-11.el9_7.3 | ALSA-2025:23210 | Dec 15, 2025 |
| keylime-verifier · ol 10 | 0:7.12.1-11.el10_1.3 | ELSA-2025-23201 | Dec 16, 2025 |
| keylime-verifier · ol 9 | 0:7.12.1-11.el9_7.3 | ELSA-2025-23210 | Dec 16, 2025 |
| python3-keylime · RHEL 9 | 0:7.12.1-11.el9_7.3 | RHSA-2025:23210 | Dec 16, 2025 |
| python3-keylime · almalinux 9 | 7.12.1-11.el9_7.3 | ALSA-2025:23210 | Dec 15, 2025 |
| python3-keylime · ol 10 | 0:7.12.1-11.el10_1.3 | ELSA-2025-23201 | Dec 16, 2025 |
| python3-keylime · ol 9 | 0:7.12.1-11.el9_7.3 | ELSA-2025-23210 | Dec 16, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.