CVE-2026-1709: Key Exchange without Entity Authentication in Red Hat Red Hat Enterprise Linux 10
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.
AI Analysis
Technical Summary
CVE-2026-1709 identifies a critical security vulnerability in the Keylime registrar component included in Red Hat Enterprise Linux 10. Keylime is a framework designed to provide remote attestation and integrity verification using TPM (Trusted Platform Module) technology. Since version 7.12.0, the Keylime registrar fails to enforce client-side TLS authentication, allowing unauthenticated clients with network access to connect to the registrar and perform privileged administrative operations. These operations include listing all registered agents, retrieving their public TPM data, and deleting agents, effectively allowing an attacker to manipulate the attestation environment. The vulnerability arises because the registrar accepts connections without requiring client certificates, bypassing the intended mutual TLS authentication mechanism. The CVSS v3.1 score of 9.4 reflects a critical severity, with an attack vector over the network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), low confidentiality impact (C:L), but high integrity (I:H) and availability (A:H) impacts. The flaw compromises the integrity and availability of the attestation infrastructure, potentially allowing attackers to disrupt trust decisions or remove agents, which could lead to broader security breaches. No public exploits are known yet, but the vulnerability's nature makes it highly exploitable in environments where the Keylime registrar is exposed to untrusted networks or insufficiently segmented internal networks.
Potential Impact
For European organizations, especially those relying on Red Hat Enterprise Linux 10 and Keylime for TPM-based attestation and integrity verification, this vulnerability poses a significant risk. Attackers can gain unauthorized administrative control over the attestation infrastructure, undermining the trustworthiness of platform integrity measurements. This could lead to unauthorized removal or manipulation of agents, potentially allowing compromised systems to evade detection or enabling attackers to disrupt critical security monitoring. The impact extends to confidentiality, as public TPM data can be retrieved, and more critically to integrity and availability, as attackers can delete agents and disrupt attestation services. Organizations in sectors such as finance, energy, telecommunications, and government, which often deploy TPM attestation for compliance and security assurance, may face operational disruptions and increased risk of advanced persistent threats. The vulnerability could also facilitate lateral movement within networks if exploited by internal or external attackers. Given the critical severity and ease of exploitation, the threat demands urgent mitigation to protect European digital infrastructure.
Mitigation Recommendations
To mitigate CVE-2026-1709, organizations should immediately verify and enforce client-side TLS authentication on the Keylime registrar to ensure only authorized clients can perform administrative operations. If a patch is available from Red Hat, it should be applied without delay. In the absence of a patch, network-level controls such as firewall rules should restrict access to the Keylime registrar to trusted management networks or specific IP addresses. Implement network segmentation to isolate the registrar from untrusted or less secure network zones. Enable detailed logging and monitoring of registrar access to detect unauthorized connection attempts or suspicious activities. Review and tighten TLS configuration to enforce mutual authentication and strong cipher suites. Conduct regular audits of registered agents and TPM data to identify anomalies. Additionally, consider deploying intrusion detection systems (IDS) or endpoint detection and response (EDR) solutions that can alert on unusual Keylime-related activities. Finally, educate system administrators about the vulnerability and the importance of securing attestation infrastructure components.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden, Finland
CVE-2026-1709: Key Exchange without Entity Authentication in Red Hat Red Hat Enterprise Linux 10
Description
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.
AI-Powered Analysis
Technical Analysis
CVE-2026-1709 identifies a critical security vulnerability in the Keylime registrar component included in Red Hat Enterprise Linux 10. Keylime is a framework designed to provide remote attestation and integrity verification using TPM (Trusted Platform Module) technology. Since version 7.12.0, the Keylime registrar fails to enforce client-side TLS authentication, allowing unauthenticated clients with network access to connect to the registrar and perform privileged administrative operations. These operations include listing all registered agents, retrieving their public TPM data, and deleting agents, effectively allowing an attacker to manipulate the attestation environment. The vulnerability arises because the registrar accepts connections without requiring client certificates, bypassing the intended mutual TLS authentication mechanism. The CVSS v3.1 score of 9.4 reflects a critical severity, with an attack vector over the network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), low confidentiality impact (C:L), but high integrity (I:H) and availability (A:H) impacts. The flaw compromises the integrity and availability of the attestation infrastructure, potentially allowing attackers to disrupt trust decisions or remove agents, which could lead to broader security breaches. No public exploits are known yet, but the vulnerability's nature makes it highly exploitable in environments where the Keylime registrar is exposed to untrusted networks or insufficiently segmented internal networks.
Potential Impact
For European organizations, especially those relying on Red Hat Enterprise Linux 10 and Keylime for TPM-based attestation and integrity verification, this vulnerability poses a significant risk. Attackers can gain unauthorized administrative control over the attestation infrastructure, undermining the trustworthiness of platform integrity measurements. This could lead to unauthorized removal or manipulation of agents, potentially allowing compromised systems to evade detection or enabling attackers to disrupt critical security monitoring. The impact extends to confidentiality, as public TPM data can be retrieved, and more critically to integrity and availability, as attackers can delete agents and disrupt attestation services. Organizations in sectors such as finance, energy, telecommunications, and government, which often deploy TPM attestation for compliance and security assurance, may face operational disruptions and increased risk of advanced persistent threats. The vulnerability could also facilitate lateral movement within networks if exploited by internal or external attackers. Given the critical severity and ease of exploitation, the threat demands urgent mitigation to protect European digital infrastructure.
Mitigation Recommendations
To mitigate CVE-2026-1709, organizations should immediately verify and enforce client-side TLS authentication on the Keylime registrar to ensure only authorized clients can perform administrative operations. If a patch is available from Red Hat, it should be applied without delay. In the absence of a patch, network-level controls such as firewall rules should restrict access to the Keylime registrar to trusted management networks or specific IP addresses. Implement network segmentation to isolate the registrar from untrusted or less secure network zones. Enable detailed logging and monitoring of registrar access to detect unauthorized connection attempts or suspicious activities. Review and tighten TLS configuration to enforce mutual authentication and strong cipher suites. Conduct regular audits of registered agents and TPM data to identify anomalies. Additionally, consider deploying intrusion detection systems (IDS) or endpoint detection and response (EDR) solutions that can alert on unusual Keylime-related activities. Finally, educate system administrators about the vulnerability and the importance of securing attestation infrastructure components.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2026-01-30T17:00:54.761Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69864142f9fa50a62f2a748e
Added to database: 2/6/2026, 7:30:10 PM
Last enriched: 2/6/2026, 7:44:49 PM
Last updated: 2/6/2026, 8:42:19 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-25731: CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine in kovidgoyal calibre
HighCVE-2026-25636: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in kovidgoyal calibre
HighCVE-2026-25635: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in kovidgoyal calibre
HighCVE-2026-2065: Missing Authentication in Flycatcher Toys smART Pixelator
MediumCVE-2026-25640: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in pydantic pydantic-ai
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.