Skip to main content
CVE-2025-54290VulnerabilityPublished

CVE-2025-54290: Canonical LXD · Information Exposure

Affects Canonical LXDSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Canonical LXDAffected
  • =6.0
  • =5.21
Fixed in–

AI-suggested

European organizations should implement the following specific mitigations: 1) Upgrade affected LXD installations to version 6.5 or 5.21.4 (or later) as soon as patches become available from Canonical. 2) Restrict network access to the LXD API endpoints by implementing firewall rules or network segmentation to limit exposure to trusted hosts only. 3) Monitor network traffic for unusual or repeated requests containing wildcard fingerprints or other anomalous patterns targeting the image export API. 4) Employ API authentication and authorization mechanisms to ensure that only authorized users and systems can query project information. 5) Conduct regular audits of container environments to identify and remediate any unauthorized access or information leakage. 6) Integrate vulnerability scanning and threat intelligence feeds to stay informed about emerging exploits related to LXD. 7) Educate DevOps and security teams about the risks of information disclosure in container orchestration platforms and enforce secure configuration baselines.

Description

Information disclosure in image export API in Canonical LXD before 6.5 and 5.21.4 on Linux allows network attackers to determine project existence without authentication via crafted requests using wildcard fingerprints.

References

Community reviews

Loading reviews…