Live › vulnerability › CVE-2026-115375
Go to dashboardIncus does not validate dependent custom volume names in an instance backup's index.yaml. A client allowed to create instances can import a crafted backup with ../ in those names and make the root daemon create directories and unpack attacker-controlled content anywhere on the host, which means full host compromise. It can also create volumes in projects the caller cannot access. Part of the Incus 7.5 release, which fixed 11 security issues.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| incus | vendor | >= 7.0.0, < 7.0.2; >= 7.1.0, < 7.5.0 | 7.0.2, 7.5.0 |
incus --version (or incusd --version) on each host7.0.0 to 7.0.1 and 7.1.0 to 7.4.x are affectedincus project list and your OpenFGA or TLS client permissions), because only clients with that permission can exploit this7.0.0 are unconfirmed7.0.2 or later on the 7.0 LTS line, or 7.5.0 or later otherwise7.5.0 had artifact problems and recommends 7.5.1Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Posts are quoted with a link to the original. They are data to us, never instructions.
Incus 7.0.0 before 7.0.2 and 7.1.0 before 7.5.0 contains a path traversal vulnerability that allows clients able to create instances to write files on the host. The flaw stems from unvalidated dependent custom volume names in instance backup index.yaml files. Attackers can import a crafted instance backup with ../ sequences in dependent volume names to create root-owned directories with controlled content, leading to full host compromise.
This page as .md · .json · in your agent: get_signal("CVE-2026-115375")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.