On this page (7 sections)

A path traversal vulnerability, CVE-2026-130779, has been published for Incus, the container and virtual machine manager. According to the NVD record, versions before 7.6.0 accept unvalidated snapshot names when a custom volume is imported from a backup, and those names can later be used to reach paths outside the intended storage location.

If you run Incus on a host where more than one person or automation account can import custom volumes, this is worth prioritizing. The impact includes deletion of arbitrary host directories as root.

What happened

The NVD entry, published on 2026-11-18, describes a flaw in how Incus handles backups of custom storage volumes. A backup contains an index with a configuration section, and that section lists snapshot names. Incus before 7.6.0 stores those names without validating them. The upstream project's advisory is referenced as GHSA-p45f-gqqj-6qq3.

Only one independent publisher covers this story so far, and the NVD text is the only technical description available to us. Details beyond it, such as proof-of-concept availability or in-the-wild use, are not stated in the research.

How the weakness works

Path traversal happens when software builds a filesystem path from a name supplied by someone else and does not check that the name stays inside its intended directory. Sequences such as parent-directory references can then point the operation somewhere else entirely.

Per the NVD description, the attacker is a user who is permitted to import custom volumes. They craft a backup whose snapshot names contain traversal sequences. The bad names are saved on import. The harm happens later, when the volume or snapshot is used:

  • Deleting the snapshot removes arbitrary host directories, and this runs as root.
  • Renaming a snapshot operates on arbitrary paths.
  • Mounting a snapshot operates on arbitrary paths.

The delayed trigger matters for defenders. The malicious data can sit in a volume for some time before a routine cleanup or deletion activates it.

Who is affected

Any Incus deployment running a version before 7.6.0 is in scope. Realistic exposure depends on who can import custom volumes:

  • Shared or multi-tenant Incus hosts where non-administrators hold import permission.
  • Environments that import backups from outside sources, such as other teams, customers or downloaded archives.
  • Automation that restores backups from storage that more than one party can write to.

A single-user host where only the owner imports their own trusted backups has a much lower practical risk, though updating is still the right move. The NVD description says deletion runs as root on the host, so a container-level boundary is not the limit of the damage.

How to check your exposure

Start by finding the installed version. This read-only command prints the client and server versions on the Incus host, and you are looking for a server version below 7.6.0.

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

If you installed from a distribution package, you can also query the package manager. The package name can differ between distributions and repositories, so confirm it on your system first. These read-only commands list matching installed packages.

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

Then review who holds permission to import custom volumes, and which backups have been imported recently from sources you do not fully trust.

What to do now

  1. Run incus version on every Incus host and note any server below 7.6.0.
  2. Upgrade Incus to 7.6.0 or later using your normal package source or release process.
  3. Until upgraded, remove custom volume import permission from users who do not need it.
  4. Pause imports of backups that come from untrusted or shared locations.
  5. Avoid deleting, renaming or mounting snapshots of custom volumes that were imported from unverified backups until the host is patched.
  6. Take a verified, current backup of the host and important volumes before the upgrade.
  7. Read the upstream advisory GHSA-p45f-gqqj-6qq3 for any additional guidance from the maintainers.
Caution. Upgrading Incus can restart the daemon. Plan a maintenance window and check how your running instances behave during a restart before you update production hosts.
Tip. Read the release notes for the version you upgrade to, and apply updates promptly on hosts where several people can import volumes or backups.

Detection and monitoring

The research does not describe indicators of compromise, so there is no confirmed signature to search for. Sensible, general checks include:

  • Review which accounts imported custom volumes recently and from where the backup files came.
  • Look for unexpected missing directories on the host after snapshot deletions, especially outside Incus storage paths.
  • Keep file integrity or backup coverage on critical host directories so an unexpected deletion is noticed and recoverable.
  • Audit Incus permissions regularly, since the attack needs import rights.

If you suspect a host was affected, restore from a known good backup and review the guidance in Website hacked: what to do. For services running on these hosts, uptime and certificate monitoring can help you notice when something that should be running stops responding.

What we do not know yet

The NVD record gives a CVSS base score of 8.5 and high severity, but the research does not include the full vector, a list of fixed intermediate builds, or any statement about exploitation. It does not confirm whether a public proof of concept exists. Treat those points as unconfirmed until the upstream advisory or other sources state them.

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-130779: Incus before 7.6.0 contains a path traversal vulnerability that allows users permitted to import custom volumes to store unvalidated snapshot names from the…nvd.nist.gov ·
  • Incus
  • CVE-2026-130779
  • path traversal
  • containers
  • CWE-22