CVE-2026-130771 is a critical link-following flaw in Incus before 7.6.0: crafted backups or image metadata can let restricted project users read or overwrite files on the host.
What Is It
CVE-2026-130771 affects Incus, the container and virtual machine manager published under the lxc project. According to the NVD record, Incus before 7.6.0 "fails to reject special files, hard links, or symlinks in backup or image metadata." Because of this, users confined to a restricted project can reach files outside their project's boundaries.
The record describes three ways to abuse it. An attacker can import a crafted backup that contains:
- device nodes
- a hard-linked
backup.yaml - symlinks
Each of these can be used to corrupt host storage, overwrite host files, or leak other projects' data. The weakness is classified as CWE-59, Improper Link Resolution Before File Access ("Link Following").
Why It Matters
VulnCheck, the CNA, rated the flaw 9.9 (Critical) under CVSS v3.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H). Under CVSS v4.0 it scores 8.5 (High). The vector shows:
- it can be exploited over the network with low attack complexity
- it needs only low privileges and no user interaction
- its scope is changed, so the damage reaches beyond the vulnerable component, in this case the host and other tenants' projects
- integrity and availability impact are high, and confidentiality impact is low
The privilege requirement is low, and restricted projects exist to isolate tenants. That makes this a real concern for multi-tenant Incus deployments, where users are trusted inside their own project but not with the host.
The supplied CISA KEV entry is empty, so there is no KEV confirmation of active exploitation for this CVE at this time. NVD lists the record's status as "Deferred."
What's Vulnerable
- Vendor: lxc
- Product: Incus (
pkg:golang/github.com/lxc/incus/v7/cmd/incusd) - Affected: all versions before 7.6.0 (semver)
- Unaffected: 7.6.0
The exposure comes from importing backups or handling image metadata in deployments that use restricted projects.
Patch Status
The affected-version data marks Incus 7.6.0 as unaffected, so upgrading to 7.6.0 or later is the fix. The record has no KEV entry, so there is no CISA-required action or due date. Administrators running multi-tenant or restricted-project Incus environments should check the GitHub security advisory for the vendor's guidance and upgrade promptly.