Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

High severity, with a CVSS score of 7.7, published 6 November 2026.

Which products and versions are affected?

Canonical LXD ; github.com/canonical/lxd (Go) < 0.0.0-20260630083100-c5184be310b1, SEMVER:introduced=0,fixed=0.0.0-20260630083100-c5184be310b1.

Is there a fix for This vulnerability?

Yes. github.com/canonical/lxd (Go): upgrade to 0.0.0-20260630083100-c5184be310b1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

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

Check whether you run Canonical LXD or github.com/canonical/lxd (Go) 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.

LXD project restriction bypass in instance copy

Q: Is there a fix for This vulnerability?

Yes. github.com/canonical/lxd (Go): upgrade to 0.0.0-20260630083100-c5184be310b1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

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

Q: Am I affected?

Check whether you run Canonical LXD or github.com/canonical/lxd (Go) 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.

Severity: high · CVSS 7.7 · Published 2026-11-06

LXD is a container management system that isolates workloads into projects with access controls. An attacker who knows the names of a restricted project and an instance within it can bypass authorization checks to copy that instance to an accessible project, potentially exposing sensitive data stored in containers they should not have access to.

Technologies: Canonical LXD, github.com/canonical/lxd (Go). Vendors: Canonical, Go.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: High severity, with a CVSS score of 7.7, published 6 November 2026.
Which products and versions are affected?: Canonical LXD <UNKNOWN>; github.com/canonical/lxd (Go) < 0.0.0-20260630083100-c5184be310b1, SEMVER:introduced=0,fixed=0.0.0-20260630083100-c5184be310b1.
Is there a fix for This vulnerability?: Yes. github.com/canonical/lxd (Go): upgrade to 0.0.0-20260630083100-c5184be310b1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a network appliance.
Am I affected?: Check whether you run Canonical LXD or github.com/canonical/lxd (Go) 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/canonical/lxd (Go): upgrade to 0.0.0-20260630083100-c5184be310b1 or later
```
go get github.com/canonical/lxd@v0.0.0-20260630083100-c5184be310b1
```

Technical details

The vulnerability exists in the instance copy API endpoint which authorizes the target project but fails to verify that the caller has access to view the source instance from the source project. An attacker can use POST /1.0/instances with a source parameter referencing an unauthorized project to copy instances across project boundaries. This requires network access to the LXD daemon and knowledge of the project and instance names, but no authentication bypass is needed as the attacker must already have valid credentials.

Affected products

Canonical LXD <UNKNOWN>

Timeline

2026-11-06: disclosed

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