In Lima, a malicious disk image could read a single file on the host filesystem as a qcow2/vmdk backing fileGHSA-f7qw-jj9c-rpq9
LOWFix: lima-vm/lima@01dbd4dGHSA-f7qw-jj9c-rpq9 is a low-severity (CVSS 2.7) CWE-552 vulnerability in github.com/lima-vm/lima. A fix is available for github.com/lima-vm/lima — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-f7qw-jj9c-rpq9.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/lima-vm/limaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Note
The official templates of Lima, and the well-known third party products (Colima, Rancher Desktop, and Finch) are unlikely to be affected by this issue.
Impact
A virtual machine instance with a malicious disk image could read a single file on the host filesystem, even when no filesystem is mounted from the host.
To exploit this issue, the attacker has to embed the target file path (an absolute or a relative path from the instance directory) in a malicious disk image, as the qcow2 (or vmdk) backing file path string.
As Lima refuses to run as the root, it is practically impossible for the attacker to read the entire host disk via /dev/rdiskN.
Also, practically, the attacker cannot read at least the first 512 bytes (MBR) of the target file.
Patches
Patched in Lima v0.16.0, by prohibiting using a backing file path in the VM base image.
Workarounds
Do not use an untrusted disk image.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/lima-vm/lima | all versions | 0.16.0go get github.com/lima-vm/lima@v0.16.0 |
Affected Products
limalinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lima-vm/lima, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/lima-vm/lima to 0.16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f7qw-jj9c-rpq9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-f7qw-jj9c-rpq9 in your dependencies?
Find it across Go, including transitive dependencies.