Keylime allows users to register new agents by recycling existing UUIDs when using different TPM devices

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L

EPSS

• CVE-2025-13609: 0.47% estimated exploitation activity in the next 30 days; percentile 40.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

24 Nov 2025, 18:31 UTC

Last modified by the source

29 May 2026, 21:00 UTC

Source last checked

26 Oct 2026, 13:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-xh5w-g8gq-r3v9

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-xh5w-g8gq-r3v9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-13609

Advisory: Keylime allows users to register new agents by recycling existing UUIDs when using different TPM devices
IDs: CVE-2025-13609, GHSA-xh5w-g8gq-r3v9
Record: https://patchnext.com/advisories/cve-2025-13609 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: keylime 7.13.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI keylime: affected < 7.13.0; fixed in 7.13.0

## Suggested inspection (read-only)
- `python -m pip show keylime`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on keylime.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-xh5w-g8gq-r3v9 (OSV record GHSA-xh5w-g8gq-r3v9 lists affected ranges: PyPI keylime >=0 <7.13.0 (fixed))
- Verified: https://github.com/advisories/GHSA-xh5w-g8gq-r3v9 (GitHub-reviewed advisory GHSA-xh5w-g8gq-r3v9 lists affected ranges: PyPI keylime >=0 <7.13.0)

Commands are suggestions: review each one before running it.