All vulnerabilities
GHSA-jh4v-j34r-2mgh

github.com/lxc/incus/v7/cmd/incusd: Project restriction bypass for custom volume copy with omitted source type

github.com/lxc/incus/v7/cmd/incusd
CVSS
7.7High
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)No scoreNo FIRST EPSS score in this snapshot yet
Fixed inNone listedNo source names a fixed version yet
Published25 Sep 2026Updated 25 Sep 2026GitHub

What fixes it

No source in this snapshot names a fixed version.

Description

Summary

Creating a custom storage volume with a source volume but no source.type is handled as a copy, but the source volume access check only applies when source.type is explicitly set to copy. A request that omits the type goes straight to the copy code path with a caller-controlled source.project.

Impact

Any client allowed to create custom volumes in a project can copy any custom volume from any other project on the server, including its snapshots and configuration, and read its contents, defeating project isolation.

Details

The POST /1.0/storage-pools/{pool}/volumes/custom endpoint only checks can_create_storage_volumes on the target project. The can_view check on the source volume added for CVE-2026-55621 lives in the copy arm of the source type switch, while the empty type arm calls the same copy helper without it. The official client always sets source.type to copy, so the empty form is only reachable through a crafted request.

Text from GitHub Advisory Database

Affected versions 1

  • github.com/lxc/incus/v7/cmd/incusd, go< v7.5.0GitHub