Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2025-13609 keylime

HIGH

CVE-2025-13609 is a high-severity (CVSS 8.2) CWE-694 vulnerability in keylime. A fix is available for keylime — see the affected versions and patch details below.

Keylime: keylime: registrar allows identity takeover via duplicate uuid registration

Also known asGHSA-xh5w-g8gq-r3v9PYSEC-2025-77
Published
Nov 24, 2025
Updated
Aug 12, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-13609.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2025-13609 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
🐍keylime

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIkeylimeall versions7.13.0pip install --upgrade 'keylime==7.13.0'

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keylime, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update keylime to 7.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-13609 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-13609 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-13609. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is rated Important for Red Hat products as the Keylime registrar allows an attacker to perform an identity takeover. By registering a new agent with a duplicate UUID, an attacker can overwrite an existing agent's identity, enabling impersonation and potential bypass of security controls. This…

ProductFixed inAdvisory
Red Hat Enterprise Linux 10keylime-0:7.12.1-11.el10_1.3RHSA-2025:23201
Red Hat Enterprise Linux 10.0 Extended Update Supportkeylime-0:7.12.1-2.el10_0.4RHSA-2026:0429
Red Hat Enterprise Linux 9keylime-0:7.12.1-11.el9_7.3RHSA-2025:23210
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutionskeylime-0:6.5.2-6.el9_2.1RHSA-2025:23735
Red Hat Enterprise Linux 9.4 Extended Update Supportkeylime-0:7.3.0-13.el9_4.1RHSA-2025:23852
Red Hat Enterprise Linux 9.6 Extended Update Supportkeylime-0:7.3.0-15.el9_6.1RHSA-2025:23628

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2025-13609 in your dependencies?

O3 Security finds CVE-2025-13609 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2025-13609: keylime (High 8.2) | O3 Security