← Back
CVE-2026-6420
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.
AI summary snake-internal / snake-material-v2
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: ?/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 /
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`` without authentication.
📍 Affected scope
keylime — . Attack surface: `tpm2_quote` / `quote_interval`.
🔥 Severity
Severity: ?. 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'keylime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `keylime` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade keylime to 7.14.2ステージング環境で 7.14.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
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
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-6420
- package https://github.com/keylime/keylime
- web https://github.com/keylime/keylime/security/advisories/GHSA-q8w6-w55c-ccv5
- web https://access.redhat.com/security/cve/CVE-2026-6420
- web https://bugzilla.redhat.com/show_bug.cgi?id=2458889
- web https://github.com/advisories/GHSA-q8w6-w55c-ccv5