Security Digest · Vulnerability record

CVE-2026-1709: Keylime Missing Authentication for Critical Function and Improper 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.

CVSS 9.4 Critical EPSS 5.8% · p93

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 5.8%, percentile 93: FIRST’s model estimates a 5.8% chance of exploitation activity in the next 30 days, higher than 93% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes keylime (PyPI) >= 7.12.0, < 7.12.2, fixed in 7.12.2; keylime (PyPI) = 7.13.0, fixed in 7.13.1. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

Impact

The Keylime registrar does not enforce mutual TLS (mTLS) client certificate authentication since version 7.12.0. The registrar's TLS context is configured with ssl.CERTOPTIONAL instead of ssl.CERTREQUIRED, allowing any client to connect to protected API endpoints without presenting a valid client certificate.

Who is impacted: - All Keylime deployments running versions 7.12.0 through 7.13.0 - Environments where the registrar HTTPS port (default 8891) is network-accessible to untrusted clients

What an attacker can do: - List all registered agents (GET /v2/agents/) - enumerate the entire agent inventory - Retrieve agent details (GET /v2/agents/{uuid}) - obtain public TPM keys, certificates, and network locations (IP/port) of any agent - Delete any agent (DELETE /v2/agents/{uuid}) - remove agents from the registry, disrupting attestation services

Note: The exposed TPM data (EK, AK, certificates) consists of public keys and certificates. Private keys remain protected within TPM hardware. The HMAC secret used for challenge-response validation is stored in the database but is not exposed via the API.

Weakness type: CWE-322, CWE-295, CWE-306.

Product: keylime (PyPI) · Assigned by: redhat · Published: 2026-02-06

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
PyPIkeylime>= 7.12.0, < 7.12.27.12.2
PyPIkeylime= 7.13.07.13.1
VendorProductAffected versions (per CVE record)
Red HatRed Hat Enterprise Linux 10see vendor advisory
Red HatRed Hat Enterprise Linux 10.0 Extended Update Supportsee vendor advisory
Red HatRed Hat Enterprise Linux 9see vendor advisory

Severity scores

Scored byCVSSScoreVector
redhat3.19.4 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
redhat-SADP3.19.4 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
GitHub3.19.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable yes, technical impact partial.
  • FIRST EPSS (model of 2026-10-21): 5.79% probability of exploitation activity in the next 30 days; percentile 93.

Timeline

  • — CVE record published by redhat
  • — GitHub-reviewed advisory GHSA-4jqp-9qjv-57m2 published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

  1. RHSA-2026:2224 access.redhat.com
  2. RHSA-2026:2225 access.redhat.com
  3. RHSA-2026:2298 access.redhat.com

Vulnerability records

  1. GitHub Advisory GHSA-4jqp-9qjv-57m2 github.com
  2. CVE.org record CVE-2026-1709 cve.org
  3. NVD entry CVE-2026-1709 nvd.nist.gov

Other references from the CVE record and advisory

  1. access.redhat.com access.redhat.com
  2. RHBZ#2435514 bugzilla.redhat.com
  3. security.access.redhat.com security.access.redhat.com
  4. github.com github.com
  5. github.com github.com

Critical PyPI advisories · Today’s Security Digest