On this page (7 sections)

CVE-2026-130771 is a high-severity flaw in Incus, the container and virtual machine manager. According to the NVD record, versions before 7.6.0 fail to reject special files, hard links or symlinks inside backup or image metadata. A user who is confined to a restricted project could abuse this to read or overwrite files on the host.

If you run Incus on a shared host where several teams, customers or tenants get their own restricted projects, this matters to you. If you are the only user of your Incus server, the practical risk is lower, but upgrading is still the right step.

What happened

The NVD entry, published on 2026-11-18, describes a missing validation step. When Incus handles a backup or image metadata, it does not reject entries that are not ordinary files. Those entries can be device nodes, hard links or symbolic links. The NVD record lists an upstream GitHub security advisory as its reference for the issue.

The record says attackers can import crafted backups that contain device nodes, a hard-linked backup.yaml, or symlinks. The stated outcomes are corrupting host storage, overwriting host files, or leaking data that belongs to other projects.

Only one independent publisher covers this story so far, and the available text is the short NVD description. Details such as the exact permissions needed, the code paths involved and any workaround are not in the research, so they are not stated here. Read the upstream advisory for further detail.

The weakness in plain terms

CWE-59 covers link following problems. A symlink is a file that points to another path. A hard link is a second name for the same file data. A device node is a special file that represents hardware or a kernel interface. A backup archive can carry all three. If the software that handles the archive trusts the contents, an entry can point outside the area the user is meant to touch.

Restricted projects exist to keep users inside a fenced area. This bug is dangerous because the input comes from inside that fence (an imported backup or image), yet the effect lands on the host, which is outside it. That is why the reported impact includes reading other projects' data and overwriting host files.

Who is realistically exposed

  • Hosting providers and internal platform teams that give people restricted Incus projects and let them import backups or images.
  • Labs, CI systems and shared development servers where several users have project-level access to one Incus daemon.
  • Environments that accept backup or image files from outside sources, since a crafted file is the delivery method described in the record.
  • Single-user servers where nobody untrusted can import anything have lower exposure, but they should still upgrade.

The record does not say whether unauthenticated access is possible, and it speaks of restricted project users, so treat the risk as one of privilege boundaries inside a server you already allow people to use.

How to check your exposure

First find out which Incus version each host runs. This read-only command prints the client version and, when it can reach the daemon, the server version. Run it on each Incus host. Anything below 7.6.0 is in the affected range.

Show Incus client and server version (run on each Incus host)Shell
incus version

If you installed Incus from a distribution package, you can also query the package manager. This lists installed packages whose names contain incus, so you can see their versions. Package names differ by distribution and repository, so confirm the name on your system.

List installed Incus packages and versions (Debian/Ubuntu)Shell
dpkg -l | grep -i incus
List installed Incus packages and versions (RHEL-based)Shell
rpm -qa | grep -i incus

Then list which projects exist, so you know who could reach the vulnerable import path. Run this on the Incus host and review the projects that hold restricted users.

List projects (run on the Incus host)Shell
incus project list

What to do now

  1. Inventory every Incus host and record its version with incus version.
  2. Upgrade any host below 7.6.0 to Incus 7.6.0 or later, using your normal package source or the upstream release instructions.
  3. Until you can upgrade, avoid importing backups or images from users or sources you do not fully trust.
  4. Review who holds restricted project access and remove accounts that no longer need it.
  5. Check recent backup and image imports for files you do not recognize, and review the host for unexpected changes to files outside storage you expect Incus to write to.
  6. Read the upstream advisory referenced by the NVD record for any further guidance.
  7. Confirm the new version after the upgrade with incus version on each host.
Caution. Upgrading the Incus daemon can restart the service and may interrupt management operations. Plan a maintenance window, and confirm your instances behave as expected afterwards. Back up important data first.
Tip. Patch every Incus host you run, not just the ones you know have restricted projects. Keeping all hosts on a current release shrinks the number of places an untrusted import could land.

Detection and monitoring afterwards

No indicators of compromise appear in the research, so there is no known signature to search for. Focus on behavior instead. Watch for unexpected backup or image imports into restricted projects, unusual storage errors or corruption on the host, and changes to host files that no administrator made. Keep audit logs for Incus API activity if your setup records them, and review them for imports from accounts that do not normally perform them.

If you run public services on top of Incus hosts, outside monitoring helps you notice side effects such as downtime or changed certificates. Webforta Monitor tracks uptime, certificate and DNS changes, though it cannot see inside your hypervisor or confirm this specific flaw. For the wider picture, the small business website security guide covers basic hardening habits.

Timeline

Known dates from the sources
DateEvent
2026-11-18CVE-2026-130771 published in NVD with a CVSS score of 8.5

The research contains no CISA KEV entry for this CVE and no reports of exploitation, so exploitation status is unconfirmed. That can change, so patch on your normal urgent schedule rather than waiting for confirmation.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-130771: Incus before 7.6.0 fails to reject special files, hard links, or symlinks in backup or image metadata, allowing restricted project users to read or overwrite…nvd.nist.gov ·
  • Incus
  • CVE-2026-130771
  • containers
  • symlink
  • virtualization
  • patch