Lima launches Linux virtual machines, typically on macOS, for running containerd. Prior to 2.1.3, on an instance of Lima running with the qemu driver, an arbitrary user in the VM could access /run/lima-guestagent.sock when the guest agent is enabled, which could result in running arbitrary commands with root privileges in the VM because the guest agent socket provides tunneling for arbitrary addresses, including Unix socket addresses for privileged daemons like D-Bus. This issue is fixed in version 2.1.3.
CVE-2026-53657
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EPSS
- 9.6%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (4)
Auto-updated Jul 10, 2026An arbitrary user in a QEMU VM could gain the root privilege in the VM via the guest agent socket · Advisory · lima-vm/lima · GitHub
https://github.com/lima-vm/lima/security/advisories/GHSA-2j9v-p4xj-cjw2v2.1.3
Patch available: lima-vm/lima v2.1.3
https://github.com/lima-vm/lima/releases/tag/v2.1.3commit b08cae8a670c (lima-vm/lima)
Fix landed in lima-vm/lima commit b08cae8a670c — awaiting tagged release
https://github.com/lima-vm/lima/commit/b08cae8a670cf916d5da11c48a6de76dabd89678commit 8a45892378d2 (lima-vm/lima)
Fix landed in lima-vm/lima commit 8a45892378d2 — awaiting tagged release
https://github.com/lima-vm/lima/commit/8a45892378d22f40505c31a38f786a07701b6d50Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 19:10 UTCEG score recompute
- 2026-07-12 06:31 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 17:52 UTCEG score recompute
- 2026-07-11 05:12 UTCEG score recompute
- 2026-07-10 16:33 UTCEG score recompute
- 2026-07-10 16:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-276 · CWE-668
- CVE-2014-7210EG 9.8CRITICAL
- CVE-2017-18915EG 9.8CRITICAL
- CVE-2008-7291EG 9.8CRITICAL
- CVE-2017-16128EG 9.8CRITICAL
- CVE-2017-16127EG 9.8CRITICAL
- CVE-2017-18129EG 9.8CRITICAL
- CVE-2017-16610EG 9.8EPSS 91%CRITICAL
- CVE-2017-16597EG 9.8EPSS 99%CRITICAL
- CVE-2013-0632EG 9.8 KEVEPSS 100%CRITICAL
- CVE-1999-0426EG 9.8EPSS 95%CRITICAL
Frequently asked(5)
What is CVE-2026-53657?
When was CVE-2026-53657 disclosed?
Is CVE-2026-53657 actively exploited?
What is the CVSS score of CVE-2026-53657?
How do I remediate CVE-2026-53657?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-53657
Is Your Infrastructure Affected by CVE-2026-53657?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.