GHSA-2j9v-p4xj-cjw2: High severity go/github.com/lima-vm/lima/v2 vulnerability

Published Aug 14, 2026
·
Updated

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 with sudo by design.

Workarounds - On macOS hosts, use vz driver instead of qemu (limactl create --vm-type=vz. Default since v1.0.) - Or, disable the guest agent (limactl create --plain)

Affected Software

1 affected componentFixes available
go/github.com/lima-vm/lima/v2<=2.1.2
2.1.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/lima-vm/lima/v2 to a version that resolves this vulnerability.

    Fixed in 2.1.3
  2. Upgrade

    Upgrade Lima to a version that resolves this vulnerability.

    Fixed in 2.1.3Patch 8a45892378d22f40505c31a38f786a07701b6d50
  3. Configuration

    On macOS hosts, create the Lima VM using the `vz` driver instead of `qemu` (e.g., run `limactl create --vm-type=vz`) because the guest agent socket issue is not exploitable on `vz`.

    Lima (qemu driver) guest agent usage = vz driver
  4. Configuration

    Disable the guest agent when creating the Lima VM (e.g., use `limactl create --plain`) to mitigate guest-agent socket access (note: the default user account can still run arbitrary commands as root via the guest agent socket, but mitigation guidance is to disable it).

    Lima guest agent guest agent enablement = disabled

Event History

Aug 14, 2026
Advisory Published
via GitHub·07:24 PM
Data Sourced
via GitHub·07:24 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of GHSA-2j9v-p4xj-cjw2?

The severity of GHSA-2j9v-p4xj-cjw2 is high, with a rating of 8.2.

2

What is the impact of GHSA-2j9v-p4xj-cjw2?

GHSA-2j9v-p4xj-cjw2 allows an arbitrary user in the VM to access a socket that could enable execution of commands with root privileges in the VM.

3

Who is affected by GHSA-2j9v-p4xj-cjw2?

Instances of Lima running with the qemu driver and where the guest agent is enabled are affected by GHSA-2j9v-p4xj-cjw2.

4

How do I fix GHSA-2j9v-p4xj-cjw2?

To fix GHSA-2j9v-p4xj-cjw2, ensure the guest agent is disabled or update your Lima instance to the latest version that addresses this vulnerability.

5

What versions of Lima are affected by GHSA-2j9v-p4xj-cjw2?

Specific versions of Lima prior to the patch addressing GHSA-2j9v-p4xj-cjw2 are affected, particularly those that enable the guest agent.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203