CVE-2026-1709: Keylime: keylime: authentication bypass allows unauthorized administrative operations due to missing client-side tls authentication
A flaw was found in Keylime. The Keylime registrar, since version 7.12.0, does not enforce client-side Transport Layer Security (TLS) authentication. This authentication bypass vulnerability allows unauthenticated clients with network access to perform administrative operations, including listing agents, retrieving public Trusted Platform Module (TPM) data, and deleting agents, by connecting without presenting a client certificate.
Security readout for executives and security teams
Plain-English summary
Keylime registrar deployments may accept administrative connections without requiring a client certificate. An attacker who can reach the registrar over the network could delete enrolled agents or read public TPM-related data. This can disrupt attestation operations and weaken trust monitoring for affected RHEL systems.
Executive priority
Treat as urgent where Keylime supports platform trust or compliance controls. The main business risk is unauthorized administrative disruption of attestation coverage, especially if the registrar is reachable beyond a tightly controlled management network.
Technical view
Since Keylime 7.12.0, the registrar fails to enforce client-side TLS authentication. The flaw is an authentication bypass, CWE-322, with CVSS 9.4. Reported impacts include listing agents, retrieving public TPM data, and deleting agents without credentials when network access exists.
Likely exposure
Most relevant to organizations running Keylime registrar on affected Red Hat Enterprise Linux 9, RHEL 10, or RHEL 10.0 EUS keylime packages. Exposure depends on whether the registrar service is reachable from untrusted networks.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires network reachability to the registrar, but no privileges or user interaction are required according to the CVSS vector.
Researcher notes
Do not assume broader product impact beyond the listed Red Hat Keylime packages. The strongest evidence is Red Hat and CVE metadata; no public exploit evidence is provided in the bundle. Validate exposure by service placement and affected package inventory.
Mitigation direction
Apply the applicable Red Hat security advisory guidance for affected keylime packages.
Restrict network access to Keylime registrar services to trusted management paths.
Review registrar exposure until vendor-directed remediation is complete.
Monitor Red Hat CVE and errata pages for updated remediation details.
Validation and detection
Inventory Keylime registrar deployments and package versions across RHEL 9 and RHEL 10 systems.
Confirm whether registrar endpoints are reachable from untrusted networks.
Verify client certificate authentication is enforced after remediation.
Review logs for unexpected agent listing, TPM data access, or agent deletion activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-322: 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.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-322 · source CWE mapping
Key Exchange without Entity Authentication
Key Exchange without Entity Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.