CVE-2026-130779 is a critical path traversal flaw in Incus before 7.6.0: a user who is allowed to import custom volumes can plant crafted snapshot names that later make Incus delete arbitrary host directories as root.
What Is It
Incus before version 7.6.0 does not validate snapshot names taken from the backup index configuration section when a custom volume is imported, and stores them as given. An attacker can craft a backup whose snapshot names contain traversal sequences. When those snapshots are later deleted, Incus removes arbitrary directories on the host as root. Renaming or mounting the snapshots also acts on arbitrary paths.
The weakness is classified as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory). VulnCheck disclosed it, and NVD published the record on 2026-11-18. The NVD record is currently marked "Deferred."
Why It Matters
VulnCheck rates it 9.6 CRITICAL under CVSS 3.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H) and 8.5 HIGH under CVSS 4.0. The vector shows:
- Attack: over the network, with low attack complexity and no user interaction.
- Privileges: low. The attacker only needs permission to import custom volumes.
- Scope: changed. The impact reaches beyond the vulnerable component to the host itself.
- Impact: high to integrity and availability. There is no direct impact to confidentiality.
In practice, a user with limited import rights can delete host directories as root. That means a tenant-level permission can be turned into destruction of data on the host.
KEV status: CVE-2026-130779 is not in the supplied CISA KEV data, and the CVSS exploit maturity field is "Not Defined." Neither source confirms active exploitation.
What's Vulnerable
- Vendor/Product: lxc / incus
- Package:
pkg:golang/github.com/lxc/incus/v7/cmd/incusd - Affected: all versions before 7.6.0
- Unaffected: 7.6.0
Deployments where untrusted or semi-trusted users can import custom volumes face the most direct exposure.
Patch Status
The affected-version data lists Incus 7.6.0 as unaffected. Upgrade incusd to 7.6.0 or later. Until you can upgrade, check which users have permission to import custom volumes. No CISA KEV required action or due date applies, because the CVE has no KEV entry. The GitHub security advisory below is the upstream source for remediation details.