Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-6420 medium CVSS 6.3

Vulnerability in keylime (CVE-2026-6420)

Summary

Vulnerability in keylime (CVE-2026-6420). Confidential information can be exposed externally. Exploitable via tpm2_quote. Mitigation: upgrade to 7.14.2 or later.

Original description

The description as published by the source.

A flaw was found in Keylime. An attacker with root access on an enrolled monitored machine, where the Keylime agent runs, can exploit a vulnerability in the Keylime verifier. The verifier uses a hardcoded challenge nonce for Trusted Platform Module (TPM) quote attestation instead of a cryptographically random value. This allows the attacker to stockpile valid TPM quotes and replay them to evade detection after compromising the system. This issue affects only the push model deployment.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

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-6420 has been found in keylime.
Attackers can target a specific entry point like tpm2_quote over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.3/10.
What to do: upgrade keylime to 7.14.2 or later.
If unsure, ask your IT team or search "keylime CVE-2026-6420" on the vendor's site.

CVE-2026-6420 (keylime) — CWE-1241 / CVSS v3 6.3
Attack vector: local / no user interaction
Attack surface: tpm2_quote / quote_interval
Patched: 7.14.2 — 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-1241) exists in keylime. Attackers reach the vulnerable code path via tpm2_quote.

📍 Affected scope

Check the vendor advisory for the affected versions of keylime. Attack surface: tpm2_quote / quote_interval.

🔥 Severity

Severity: Medium (CVSS 6.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 7.14.2.

🛡️ 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.14.2

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

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

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

Affected packages

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

References

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