← Back
CVE-2026-53657
high
CVSS 8.2
Vulnerability in github.com/lima-vm/lima/v2 (CVE-2026-53657)
Summary
vulnerability in github.com/lima-vm/lima/v2 (CVE-2026-53657). Successful exploitation can lead to full system takeover. Exploitable via ``qemu``. Mitigation: upgrade to `2.1.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-53657** has been found in github.com/lima-vm/lima/v2.
Attackers can target a specific entry point like ``qemu`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.2/10.
What to do: upgrade github.com/lima-vm/lima/v2 to **2.1.3** or later.
If unsure, ask your IT team or search "github.com/lima-vm/lima/v2 CVE-2026-53657" on the vendor's site.
CVE-2026-53657 (github.com/lima-vm/lima/v2) — CWE-276 / CVSS v3 8.2
Attack vector: local / no user interaction
Attack surface: `qemu` / `sudo`
Patched: `2.1.3` — 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-276) exists in github.com/lima-vm/lima/v2. Attackers reach the vulnerable code path via ``qemu`` without authentication.
📍 Affected scope
github.com/lima-vm/lima/v2 — . Attack surface: `qemu` / `sudo`.
🔥 Severity
Severity: High (CVSS 8.2/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.1.3**.
🛡️ 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 'github.com/lima-vm/lima/v2' .` 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 'github.com/lima-vm/lima/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/lima-vm/lima/v2` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/lima-vm/lima/v2 to 2.1.3ステージング環境で 2.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/lima-vm/lima/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.3"}]}]
References
- web https://github.com/lima-vm/lima/commit/8a45892378d22f40505c31a38f786a07701b6d50
- web https://github.com/lima-vm/lima/commit/b08cae8a670cf916d5da11c48a6de76dabd89678
- web https://github.com/lima-vm/lima/releases/tag/v2.1.3
- web https://github.com/lima-vm/lima/security/advisories/GHSA-2j9v-p4xj-cjw2
- web https://nvd.nist.gov/vuln/detail/CVE-2026-53657
- web https://github.com/advisories/GHSA-2j9v-p4xj-cjw2