Security readout for executives and security teams
Plain-English summary
Keylime can let a highly privileged attacker register a different TPM-backed agent while claiming an existing agent UUID. That can replace the legitimate agent identity, allowing impersonation and possible bypass of attestation-based trust decisions.
Executive priority
Treat as high priority where Keylime supports platform trust, compliance, or workload admission decisions. The main risk is not data theft alone; it is false trust in an impersonating system.
Technical view
The registrar accepts duplicate UUID registration in a way that can overwrite an existing agent identity. Red Hat rates this high, CVSS 8.2, with network access, low complexity, high privileges, no user interaction, and changed scope.
Likely exposure
Exposure is most likely in environments running affected Red Hat keylime packages on RHEL 9, RHEL 10, and listed EUS/E4S streams where Keylime registrar enrollment is reachable to privileged actors.
Exploitation context
The bundle does not show KEV listing or confirmed active exploitation. Exploitation requires high privileges and the ability to register an agent, but impact is significant because it targets identity and trust enforcement.
Researcher notes
Evidence identifies duplicate UUID handling in Keylime registrar as the core flaw. The bundle does not provide exploit proof, patch diff details, or a universal upstream version range, so validation should stay tied to vendor advisories.
Mitigation direction
- Review the relevant Red Hat errata for your RHEL stream.
- Apply vendor-provided keylime updates where available.
- Limit registrar access to authorized enrollment paths only.
- Monitor for duplicate UUID registrations or unexpected agent replacement.
- Check Keylime project issue and Red Hat CVE page for updated guidance.
Validation and detection
- Inventory systems running keylime on affected Red Hat products.
- Confirm installed keylime package versions against Red Hat advisories.
- Review registrar logs for duplicate UUID enrollment events.
- Verify agent UUIDs map to expected TPM identities.
- Test fixes in staging before production rollout.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-694: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-13609 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L2.35.3redhatVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2025:23201CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2025:23210CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2025:23628CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2025:23735CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2025:23852CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:0429CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2025-13609CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2416761CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/keylime/keylime/issues/1820CVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Multiple Resources with Duplicate Identifier
Use of Multiple Resources with Duplicate Identifier represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.