CVE-2025-54290: Canonical LXD Project Existence Determination Through Error Handling in Image Export Function

CVE-2025-54290 · Severity: medium · CVSS 4 · Published 2025-11-05

Canonical LXD Project Existence Determination Through Error Handling in Image Export Function in github.com/canonical/lxd

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

Quick answers

Is CVE-2025-54290 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-54290 being exploited in the wild.
How severe is CVE-2025-54290?
Medium severity, with a CVSS score of 4, published 5 November 2025.
Which products and versions are affected?
github.com/canonical/lxd (Go) ECOSYSTEM:introduced=4.0,fixed=5.21.4, SEMVER:introduced=0.0.0-20200331193331-03aab09f5b5c,fixed=0.0.0-20250827065555-0494f5d47e41.
Is there a fix for CVE-2025-54290?
Yes. github.com/canonical/lxd (Go): upgrade to 0.0.0-20250827065555-0494f5d47e41, 5.21.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-54290?
Check whether you run 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-20250827065555-0494f5d47e41, 5.21.4 or later
    go get github.com/canonical/lxd@v5.21.4

Affected products

  • github.com/canonical/lxd (Go) ECOSYSTEM:introduced=4.0,fixed=5.21.4, SEMVER:introduced=0.0.0-20200331193331-03aab09f5b5c,fixed=0.0.0-20250827065555-0494f5d47e41

Identifiers

  • CVE-2025-54290
  • GHSA-p3x5-mvmp-5f35
  • GO-2025-4002

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