Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-1709 critical CVSS 9.4

Vulnerability in keylime (CVE-2026-1709)

Summary

Vulnerability in keylime (CVE-2026-1709). Data can be tampered with by attackers. Mitigation: upgrade to 7.12.0 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-1709 has been found in keylime.
Data can be tampered with by attackers. CVSS score: 9.4/10.
What to do: upgrade keylime to 7.12.0 or later.
If unsure, ask your IT team or search "keylime CVE-2026-1709" on the vendor's site.

CVE-2026-1709 (keylime) — CWE-322 / CVSS v3 9.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 7.12.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-322) exists in keylime.

📍 Affected scope

Check the vendor advisory for the affected versions of keylime.

🔥 Severity

Severity: Critical (CVSS 9.4/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 7.12.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'keylime' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'keylime' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で keylime を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade keylime to 7.12.0

    ステージング環境で 7.12.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI keylime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.12.0"}]}]
pip keylime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.13.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details