Is CVE-2026-55622 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55622 being exploited in the wild.

How severe is CVE-2026-55622?

High severity, with a CVSS score of 7.7, published 21 August 2026.

Which products and versions are affected?

github.com/lxc/incus (Go) SEMVER:introduced=0; github.com/lxc/incus/v6 (Go) SEMVER:introduced=0; github.com/lxc/incus/v7 (Go) SEMVER:introduced=0,fixed=7.2.0; github.com/lxc/incus/v7/cmd/incusd (Go) < 7.2.0, SEMVER:introduced=0,fixed=7.2.0.

Is there a fix for CVE-2026-55622?

Yes. github.com/lxc/incus/v7 (Go): upgrade to 7.2.0 or later; github.com/lxc/incus/v7/cmd/incusd (Go): upgrade to 7.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55622 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-55622?

Check whether you run github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go) or one of the others listed 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.

CVE-2026-55622: Incus project restriction bypass in instance copy

Q: Is there a fix for CVE-2026-55622?

Yes. github.com/lxc/incus/v7 (Go): upgrade to 7.2.0 or later; github.com/lxc/incus/v7/cmd/incusd (Go): upgrade to 7.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-55622 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-55622?

Check whether you run github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go) or one of the others listed 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.

CVE-2026-55622 · Severity: high · CVSS 7.7 · Published 2026-08-21

Incus is a container management platform that isolates workloads using project-based access controls. A flaw in the instance copy feature bypasses these project restrictions, allowing an authenticated user to copy containers from restricted projects into projects they can access. An attacker could exploit this to steal sensitive configuration, credentials, or data from instances they should not have permission to view, leading to unauthorized information disclosure and potential system compromise.

Technologies: github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go), github.com/lxc/incus/v7/cmd/incusd (Go). Vendors: Go.

Quick answers

Is CVE-2026-55622 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55622 being exploited in the wild.
How severe is CVE-2026-55622?: High severity, with a CVSS score of 7.7, published 21 August 2026.
Which products and versions are affected?: github.com/lxc/incus (Go) SEMVER:introduced=0; github.com/lxc/incus/v6 (Go) SEMVER:introduced=0; github.com/lxc/incus/v7 (Go) SEMVER:introduced=0,fixed=7.2.0; github.com/lxc/incus/v7/cmd/incusd (Go) < 7.2.0, SEMVER:introduced=0,fixed=7.2.0.
Is there a fix for CVE-2026-55622?: Yes. github.com/lxc/incus/v7 (Go): upgrade to 7.2.0 or later; github.com/lxc/incus/v7/cmd/incusd (Go): upgrade to 7.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55622 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-55622?: Check whether you run github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go) or one of the others listed 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

github.com/lxc/incus/v7 (Go): upgrade to 7.2.0 or later
```
go get github.com/lxc/incus/v7@v7.2.0
```
github.com/lxc/incus/v7/cmd/incusd (Go): upgrade to 7.2.0 or later
```
go get github.com/lxc/incus/v7/cmd/incusd@v7.2.0
```

Technical details

The vulnerability is an authorization bypass in the instance copy API endpoint (POST /1.0/instances). While the endpoint correctly checks if the caller has permission to create instances in the target project, it fails to validate whether the caller can access the source instance in the source project. The vulnerable code in cmd/incusd/instances_post.go loads the source instance directly from req.Source.Project without performing access control checks. An attacker needs valid credentials restricted to one project, knowledge of an instance name in another restricted project, and network access to the Incus server. The copy operation is limited to the same server, but once copied, instances can be moved between servers. The fix requires adding authorization checks before loading the source instance. Version 7.2.0 and later contain the patch.

Affected products

LXC Incus < 7.2.0

Identifiers

CVE-2026-55622
GHSA-c9f5-j9c3-mhrg
GO-2026-6319

Timeline

2026-06-25: disclosed: Published in GitHub Advisory Database
2026-06-25: patched: Fix included in Incus 7.2.0
2026-08-28: advisory: Formal advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.