Quick answers
- Is CVE-2026-115375 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115375 being exploited in the wild.
- How severe is CVE-2026-115375?
- Critical severity, with a CVSS score of 9.9, published 22 October 2026.
- Which products and versions are affected?
- LXC Incus 7.0.0 before 7.0.2; 7.1.0 before 7.5.0.
- Is there a fix for CVE-2026-115375?
- Yes: fixed in 7.0.2, 7.5.0. Until then: Only allow trusted clients to create instances. Restrict instance creation permissions to users and applications that are fully trusted not to import malicious backups. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115375 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-115375?
- Check whether you run LXC Incus at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 7.0.2, 7.5.0
Only allow trusted clients to create instances. Restrict instance creation permissions to users and applications that are fully trusted not to import malicious backups.
Technical details
The vulnerability is a path traversal (CWE-22, CWE-23) in the instance backup import handler. When restoring an instance backup, the code validates the instance and snapshot names but fails to sanitize the names of dependent custom volumes listed in the backup's index.yaml file. An attacker can inject ../ sequences into these volume names to escape the storage pool directory and create files at arbitrary paths on the host filesystem. Requires authentication with instance creation privileges and network access to the Incus daemon.
Affected products
- LXC Incus 7.0.0 before 7.0.2; 7.1.0 before 7.5.0
Timeline
- 2026-09-25: disclosed: GitHub Security Advisory published
- 2026-10-22: advisory: Public disclosure