CVE-2026-1709: Keylime Critical Authentication Bypass Vulnerability
Summary
CVE-2026-1709: Keylime Missing Authentication for Critical Function and Improper Authentication. Affects keylime across 2 version ranges.
>= 7.12.0, < 7.12.2
>= 7.13.0, < 7.13.1
Fixed in 7.12.2 or 7.13.1, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Keylime is an open-source project that provides a framework for remote attestation of trusted computing systems. It enables secure communication between a verifier and a tenant, ensuring that only trusted agents are allowed to participate in the attestation process. The vulnerability in question arises from a misconfiguration in the mutual TLS (mTLS) authentication mechanism, which is critical for securing communications between clients and the Keylime registrar.
Vulnerability Detail
The Keylime registrar, starting from version 7.12.0, fails to enforce mutual TLS (mTLS) client certificate authentication due to its TLS context being set to 'ssl.CERT_OPTIONAL' instead of 'ssl.CERT_REQUIRED'. This misconfiguration allows any client to connect to sensitive API endpoints without presenting a valid client certificate. As a result, an attacker can list all registered agents, retrieve sensitive agent details, and delete agents from the registry, potentially disrupting attestation services and exposing public TPM data.
How To Fix
Latest published version: 7.14.3 as of 22 Oct 2026
pip install --upgrade "keylime==7.14.3"
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
>= 7.12.0, < 7.12.27.12.2pip install --upgrade "keylime==7.12.2" -
>= 7.13.0, < 7.13.17.13.1pip install --upgrade "keylime==7.13.1"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
text
If immediate upgrading is not feasible, consider implementing one of the following workarounds:
- Network Isolation: Restrict access to the registrar's HTTPS port (default 8891) using firewall rules to allow only trusted hosts. Example using iptables:
iptables -A INPUT -p tcp --dport 8891 -s <verifier_ip> -j ACCEPT
iptables -A INPUT -p tcp --dport 8891 -s <tenant_ip> -j ACCEPT
iptables -A INPUT -p tcp --dport 8891 -j DROP
- Reverse Proxy with mTLS Enforcement: Deploy a reverse proxy (e.g., nginx) that enforces client certificate authentication. Example nginx configuration:
server {
listen 8891 ssl;
ssl_certificate /path/to/server.crt;
ssl_certificate_key /path/to/server.key;
ssl_client_certificate /path/to/ca.crt;
ssl_verify_client on; # Enforce client certificates
location / {
proxy_pass https://localhost:8892; # Internal registrar port
}
}
Conclusion
CVE-2026-1709 is a critical vulnerability in Keylime that allows unauthorized access to sensitive API endpoints due to improper authentication settings. Users are strongly advised to upgrade to the patched versions or implement workarounds to mitigate the risk. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for keylime →
FAQ
The vulnerability allows unauthorized clients to access sensitive API endpoints, potentially leading to data exposure and service disruption.
Keylime versions 7.12.0 through 7.13.0 are affected by this vulnerability.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
The CVSS score for CVE-2026-1709 is 9.4, indicating a critical severity level.
If you cannot upgrade immediately, implement network isolation or set up a reverse proxy to enforce mTLS as a temporary measure.
Related vulnerabilities
Recent vulnerabilities recorded for keylime.