# CVE-2026-86335: Canonical LXD missing authorization in imageDownload

Source: https://junglewise.ai/threats/cve-2026-86335-missing-authorization-in-imagedownload-in-canonical-lxd-before-5  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-28. Updated: 2026-09-28  
License: CC BY 4.0 with a link back

CVE-2026-86335 · Severity: medium · CVSS 6.3 · Published 2026-09-28

LXD is a container management system that isolates workloads across projects. A flaw in image access control allows a user restricted to one project to download private container images from other projects by reusing image fingerprints, potentially exposing sensitive application configurations or data embedded in those images.

Technologies: [Canonical LXD](https://junglewise.ai/threats/technologies/lxd). Vendors: [Canonical](https://junglewise.ai/threats/vendors/canonical).

## Quick answers

**Is CVE-2026-86335 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-86335 being exploited in the wild.

**How severe is CVE-2026-86335?** Medium severity, with a CVSS score of 6.3, published 28 September 2026.

**Which products and versions are affected?** Canonical LXD before 5.0.10, before 5.21.8, before 6.10.

**Is there a fix for CVE-2026-86335?** A patch was published on 2026-09: Fix merged in PR #18987 (main branch) and PR #19001 (release-6.9) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-86335 attacked?** It is attacked with local access, in a network appliance.

**Am I affected by CVE-2026-86335?** Check whether you run Canonical LXD 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.

## Technical details

Missing authorization in the imageDownload function fails to validate project boundaries, allowing project-restricted clients to access private images from other projects via local fingerprint reuse during image or instance import requests. The vulnerability requires local access to the LXD daemon and affects versions before 5.0.10, 5.21.8, and 6.10. A fix restricting image reuse to cached images with identical image source has been merged.

## Affected products

- Canonical LXD before 5.0.10, before 5.21.8, before 6.10

## Timeline

- 2026-09-28: disclosed
- 2026-09: patched: Fix merged in PR #18987 (main branch) and PR #19001 (release-6.9)

## References

- [https://github.com/canonical/lxd/pull/18987](https://github.com/canonical/lxd/pull/18987)
- [https://github.com/canonical/lxd/pull/19001](https://github.com/canonical/lxd/pull/19001)

## Related threats

- [LXD project restriction bypass in instance copy](https://junglewise.ai/threats/lxd-has-project-restriction-bypass-in-instance-copy-across-projects-48d466e0)
- [Canonical LXD improper certificate validation in HTTPS listener](https://junglewise.ai/threats/cve-2026-112816-improper-certificate-validation-in-the-https-listener-in)
- [Canonical LXD custom storage volume authorization bypass](https://junglewise.ai/threats/cve-2026-97335-incorrect-authorization-in-the-custom-storage-volume-creation)
- [Canonical LXD arbitrary file write via symlink in migration stream](https://junglewise.ai/threats/cve-2026-87799-improper-link-resolution-in-the-migration-receive-path-in)
- [Canonical LXD improper symlink resolution in recursive file pull](https://junglewise.ai/threats/cve-2026-87798-improper-link-resolution-in-the-recursive-file-pull-feature-of)