GHSA-3g2j-vm47-x4mj
LXD vulnerable to a local privilege escalation through custom storage volumes
Impact
This affects any LXD user in an environment where an unprivileged user may have root access to a container with an attached custom storage volume that has the security.shifted property set to true as well as access to the host as an unprivileged user.
The most common case for this would be systems using lxd-user with the less privileged lxd group to provide unprivileged users with an isolated restricted access to LXD. Such users may be able to create a custom storage volume with the necessary property (depending on kernel and filesystem support) and can then write a setuid binary from within the container which can be executed as an unprivileged user on the host to gain root privileges.
Patches
Patches for this issue are available:
- LXD 6 series: https://github.com/canonical/lxd/pull/16904
- LXD 5.21 LTS series: https://github.com/canonical/lxd/pull/16922
- LXD 5.0 LTS series: https://github.com/canonical/lxd/pull/16923
- LXD 4.0 LTS series: https://github.com/canonical/lxd/pull/16924
The first commit changes the permissions for any new storage pool, the later commit adds a patch that applies it on startup to all existing storage pools.
These fixes are also available in the associated candidate snap channels for each LTS series:
- 5.21/candidate (5.21.4-8a3cf61)
- 5.0/candidate (5.0.5-5c60378)
- 4.0/candidate (4.0.10-35a8127)
We will be preparing intermediate releases to the associated stable snap channels shortly.
Workarounds
Permissions can be manually restricted until a patched version of LXD is deployed.
This is done with:
sudo nsenter --mount=/run/snapd/ns/lxd.mnt -- chmod 0700 /var/snap/lxd/common/lxd/storage-pools/*/{custom*,virtual-machines*,images}
sudo nsenter --mount=/run/snapd/ns/lxd.mnt -- chmod 0711 /var/snap/lxd/common/lxd/storage-pools/*/{containers*,buckets*}
Those are the same permissions which will be applied by the patched LXD for both new and existing storage pools.
References
This was reported to Incus publicly on Github here:
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
What each source reports
GitHub Advisories Score used
LXD vulnerable to a local privilege escalation through custom storage volumes
Impact
This affects any LXD user in an environment where an unprivileged user may have root access to a container with an attached custom storage volume that has the security.shifted property set to true as well as access to the host as an unprivileged user.
The most common case for this would be systems using lxd-user with the less privileged lxd group to provide unprivileged users with an isolated restricted access to LXD. Such users may be able to create a custom storage volume with the necessary property (depending on kernel and filesystem support) and can then write a setuid binary from within the container which can be executed as an unprivileged user on the host to gain root privileges.
Patches
Patches for this issue are available:
- LXD 6 series: https://github.com/canonical/lxd/pull/16904
- LXD 5.21 LTS series: https://github.com/canonical/lxd/pull/16922
- LXD 5.0 LTS series: https://github.com/canonical/lxd/pull/16923
- LXD 4.0 LTS series: https://github.com/canonical/lxd/pull/16924
The first commit changes the permissions for any new storage pool, the later commit adds a patch that applies it on startup to all existing storage pools.
These fixes are also available in the associated candidate snap channels for each LTS series:
- 5.21/candidate (5.21.4-8a3cf61)
- 5.0/candidate (5.0.5-5c60378)
- 4.0/candidate (4.0.10-35a8127)
We will be preparing intermediate releases to the associated stable snap channels shortly.
Workarounds
Permissions can be manually restricted until a patched version of LXD is deployed.
This is done with:
sudo nsenter --mount=/run/snapd/ns/lxd.mnt -- chmod 0700 /var/snap/lxd/common/lxd/storage-pools/*/{custom*,virtual-machines*,images}
sudo nsenter --mount=/run/snapd/ns/lxd.mnt -- chmod 0711 /var/snap/lxd/common/lxd/storage-pools/*/{containers*,buckets*}
Those are the same permissions which will be applied by the patched LXD for both new and existing storage pools.
References
This was reported to Incus publicly on Github here:
- Record
GHSA-3g2j-vm47-x4mj- CVSS 4.0
- 8.6 High
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - Weakness
- CWE-269
- Updated
- 2026-11-02
OSV
LXD vulnerable to a local privilege escalation through custom storage volumes
Impact
This affects any LXD user in an environment where an unprivileged user may have root access to a container with an attached custom storage volume that has the security.shifted property set to true as well as access to the host as an unprivileged user.
The most common case for this would be systems using lxd-user with the less privileged lxd group to provide unprivileged users with an isolated restricted access to LXD. Such users may be able to create a custom storage volume with the necessary property (depending on kernel and filesystem support) and can then write a setuid binary from within the container which can be executed as an unprivileged user on the host to gain root privileges.
Patches
Patches for this issue are available:
- LXD 6 series: https://github.com/canonical/lxd/pull/16904
- LXD 5.21 LTS series: https://github.com/canonical/lxd/pull/16922
- LXD 5.0 LTS series: https://github.com/canonical/lxd/pull/16923
- LXD 4.0 LTS series: https://github.com/canonical/lxd/pull/16924
The first commit changes the permissions for any new storage pool, the later commit adds a patch that applies it on startup to all existing storage pools.
These fixes are also available in the associated candidate snap channels for each LTS series:
- 5.21/candidate (5.21.4-8a3cf61)
- 5.0/candidate (5.0.5-5c60378)
- 4.0/candidate (4.0.10-35a8127)
We will be preparing intermediate releases to the associated stable snap channels shortly.
Workarounds
Permissions can be manually restricted until a patched version of LXD is deployed.
This is done with:
sudo nsenter --mount=/run/snapd/ns/lxd.mnt -- chmod 0700 /var/snap/lxd/common/lxd/storage-pools/*/{custom*,virtual-machines*,images}
sudo nsenter --mount=/run/snapd/ns/lxd.mnt -- chmod 0711 /var/snap/lxd/common/lxd/storage-pools/*/{containers*,buckets*}
Those are the same permissions which will be applied by the patched LXD for both new and existing storage pools.
References
This was reported to Incus publicly on Github here:
- Record
GHSA-3g2j-vm47-x4mj- CVSS 4.0
- 8.6 High
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - Weakness
- CWE-269
- Updated
- 2026-11-02
OSVGO-2025-4121No score
LXD vulnerable to a local privilege escalation through custom storage volumes in lxd in github.com/canonical/lxd
LXD vulnerable to a local privilege escalation through custom storage volumes in lxd in github.com/canonical/lxd
- Record
GO-2025-4121- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/canonical/lxdGo | before 0.0.0-20251110144034-698854d0164f | 0.0.0-20251110144034-698854d0164f |
github.com/canonical/lxdGo | All versions | None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-3g2j-vm47-x4mj is a high vulnerability (CVSS 8.6) in github.com/canonical/lxd, published November 13, 2025. No source lists public exploit code. Fixed in github.com/canonical/lxd 0.0.0-20251110144034-698854d0164f.
References
github.com/canonical/lxd/security/advisories/GHSA-3g2j-vm47-x4mj