Cyber Resilience

CVE-2026-1709

Redhat Enterprise Linux 10.0 … 9.0

Published
06 February 2026
Modified
15 July 2026
CVSS Score v3.1 9.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
EPSS Score 0.054 92th percentile
Risk Priority 75 floored blend · peak EPSS

Summary

CVE-2026-1709 is a critical-severity Key Exchange without Entity Authentication (CWE-322) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 9.4 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Adversary-in-the-Middle (T1557); ranked in the top 8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-1709 is an authentication bypass vulnerability in the Keylime registrar component, affecting versions since 7.12.0. The flaw arises because the registrar fails to enforce client-side Transport Layer Security (TLS) authentication, allowing clients to connect without presenting a required client certificate. This issue, associated with CWE-322, has a CVSS v3.1 base score of 9.4 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H), indicating critical severity due to high impacts on integrity and availability.

Any unauthenticated attacker with network access to the Keylime registrar can exploit this vulnerability to perform administrative operations. Successful exploitation enables listing agents, retrieving public Trusted Platform Module (TPM) data, and deleting agents, potentially disrupting Keylime's agent management and attestation functions without requiring privileges or user interaction.

Red Hat has issued multiple security advisories addressing this vulnerability, including RHSA-2026:2224, RHSA-2026:2225, and RHSA-2026:2298, along with detailed information on their CVE page and Bugzilla entry (ID 2435514). These resources provide guidance on applying patches to mitigate the authentication bypass.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

Trusted Platform Module (TPM) data, and deleting agents, by connecting without presenting a client certificate.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-38200Same product: Keylime Keylime
CVE-2023-38201Same product: Keylime Keylime
CVE-2025-62501Shared CWE-322
CVE-2026-1354Shared CWE-322
CVE-2025-20163Shared CWE-322
CVE-2026-45361Shared CWE-322
CVE-2024-47519Shared CWE-322
CVE-2024-4871Shared CWE-322
CVE-2025-13914Shared CWE-322
CVE-2024-6572Shared CWE-322

Affected Assets

redhat
enterprise linux
10.0, 9.0
redhat
enterprise linux eus
10.0
redhat
enterprise linux for arm 64
10.0_aarch64, 9.0_aarch64
redhat
enterprise linux for arm 64 eus
10.0_aarch64
redhat
enterprise linux for ibm z systems
10.0_s390x, 9.0_s390x
redhat
enterprise linux for ibm z systems eus
10.0_s390x
redhat
enterprise linux for power little endian
10.0_ppc64le, 9.0_ppc64le
redhat
enterprise linux for power little endian eus
10.0_ppc64le
keylime
keylime
≤ 7.12.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V12.1.3

Mitigating Controls (NIST 800-53 r5) AI

Requiring device identification and authentication before establishing connections prevents unauthenticated key exchanges with unknown devices.

Requiring unique identification and authentication of users before any privileged action stops key exchange from occurring with unauthenticated parties.

Requiring identification and authentication of non-organizational users blocks key exchange with unauthenticated external actors.

Requiring proper cryptographic key establishment and management directly stops unauthenticated key-exchange implementations.

Issuing or obtaining PKI certificates under an approved policy supplies the entity authentication missing from unauthenticated key exchange.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 mostly match
prevents

Requiring authentication of services/hardware prevents unauthenticated key exchange.

PR.AA-02 partial match
prevents

Identity proofing and binding directly supports verifying actors before key exchange.

PR.AA-04 partial match
prevents

Verifying identity assertions mitigates the missing entity authentication in key exchange.

PR.DS-02 partial match
prevents

Protecting data-in-transit implies use of authenticated key exchange but does not explicitly require entity authentication.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Use of cryptography mandates authenticated key-exchange mechanisms, directly addressing the lack of entity authentication.

finds

Security testing can detect missing entity authentication during key exchange.

prevents

Secure authentication directly prevents unauthenticated key exchange by requiring verified identities before keys are established.

prevents

Identity management provides the verified identities required before key exchange occurs.

mitigates

Network security policies can require authenticated channels, indirectly reducing the risk of unauthenticated key exchange.

mitigates

Security of network services includes requirements for authenticated key exchange in service protocols.

References