Quick answers
- Is CVE-2026-115376 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115376 being exploited in the wild.
- How severe is CVE-2026-115376?
- High severity, with a CVSS score of 7.7, published 22 October 2026.
- Which products and versions are affected?
- Canonical Incus 7.0.1 before 7.0.2; 7.2.0 before 7.5.0.
- Is there a fix for CVE-2026-115376?
- Yes: fixed in Incus 7.0.2, 7.5.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115376 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-115376?
- Check whether you run Canonical 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: Incus 7.0.2, 7.5.0
Technical details
An improper access control vulnerability exists in the custom volume copy endpoint (POST /1.0/storage-pools/{pool}/volumes/custom) where the authorization check for source volumes is only applied when source.type is explicitly set to "copy". Requests omitting source.type bypass this check and proceed directly to the copy logic with caller-controlled source.project, allowing any user with volume creation permissions in their project to copy and read volumes from any other project on the server, including snapshots and configuration.
Affected products
- Canonical Incus 7.0.1 before 7.0.2; 7.2.0 before 7.5.0
Timeline
- 2026-09-25: advisory: GitHub security advisory published
- 2026-10-22: disclosed: Vulnerability publicly disclosed