LXD has restricted project bypass leading to arbitrary command execution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Reported from https://github.com/lxc/incus/security/advisories/GHSA-48q5-w887-33wv

Summary Instance snapshots ignore the `restricted.containers.lowlevel=block` setting; allowing for arbitrary command execution on the Incus server by abusing lowlevel hooks such as `raw.lxc` and `raw.qemu`.

Details Instance snapshots ignore the `restricted.containers.lowlevel=block` setting; allowing for arbitrary command execution on the Incus server by abusing lowlevel hooks such as `raw.lxc` and `raw.qemu`. As snapshots can be moved from one server to another, a malicious instance+snapshot can be crafted locally, moved to a restricted project and the snapshot restored for arbitrary command execution. In practice, this allows a malicious actor to execute arbitrary commands on the host with root privileges.

PoC ```

remote, restricted incus project set rem:project restricted.true incus project set rem:project restricted.containers.lowlevel=block

locally, unrestricted project incus init…

Published by the source

6 Nov 2026, 19:51 UTC

Last modified by the source

6 Nov 2026, 20:00 UTC

Source last checked

7 Nov 2026, 06:05 UTC

1. Revision 2 · amended · 7 Nov 2026

   Amended from osv record GHSA-47w9-6r3f-938g

2. Revision 1 · created · 6 Nov 2026

   Published from ghsa record GHSA-47w9-6r3f-938g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-47w9-6r3f-938g

Advisory: LXD has restricted project bypass leading to arbitrary command execution
IDs: GHSA-47w9-6r3f-938g
Record: https://patchnext.com/advisories/ghsa-47w9-6r3f-938g (revision 2, source checked 7 Nov 2026, 06:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/canonical/lxd 0.0.0-20260630083100-c5184be310b1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/canonical/lxd: affected < 0.0.0-20260630083100-c5184be310b1; fixed in 0.0.0-20260630083100-c5184be310b1

## Suggested inspection (read-only)
- Go github.com/canonical/lxd: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/canonical/lxd.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-47w9-6r3f-938g (GitHub-reviewed advisory GHSA-47w9-6r3f-938g lists affected ranges: Go github.com/canonical/lxd >=0 <0.0.0-20260630083100-c5184be310b1)
- Verified: https://osv.dev/vulnerability/GHSA-47w9-6r3f-938g (OSV record GHSA-47w9-6r3f-938g lists affected ranges: Go github.com/canonical/lxd >=0 <0.0.0-20260630083100-c5184be310b1 (fixed))

Commands are suggestions: review each one before running it.