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.
Original description
The description as published by the source.
Impact
On an instance of Lima running with qemu driver, an arbitrary user in the VM could access /run/lima-guestagent.sock when the guest agent is enabled.
This could result in running an arbitrary command with the root privileges in the VM (not on the host), as lima-guestagent.sock provides the tunneling service for an arbitrary address, including a Unix socket address for privileged daemons like D-Bus.
This vulnerability is not exploitable on vz driver, as the guest agent uses vsocks instead of Unix sockets.
Patches
Patched in Lima v2.1.3 (8a45892378d22f40505c31a38f786a07701b6d50)
[!NOTE]
The default user account in the VM can still run an arbitrary command as the root via the guest agent socket.
This is not a vulnerability, as the user can already run an arbitrary command withsudoby design.
Workarounds
- On macOS hosts, use
vzdriver instead ofqemu(limactl create --vm-type=vz. Default since v1.0.) - Or, disable the guest agent (
limactl create --plain)
Source: NIST National Vulnerability Database 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-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.
A vulnerability (CWE-276) exists in github.com/lima-vm/lima/v2. Attackers reach the vulnerable code path via qemu.
Check the vendor advisory for the affected versions of github.com/lima-vm/lima/v2. Attack surface: qemu / sudo.
Severity: High (CVSS 8.2/10). Successful exploitation can lead to full system takeover.
Update to 2.1.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/lima-vm/lima/v2 to 2.1.3ステージング環境で 2.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com