CVE-2025-54290: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in Canonical LXD
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.
AI Analysis
Technical Summary
CVE-2025-54290 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) affecting Canonical's LXD container hypervisor software on Linux platforms. The flaw exists in the image export API of LXD versions prior to 6.5 and 5.21.4, where crafted network requests using wildcard fingerprints can be sent without authentication to the API. This allows an attacker to infer the existence of projects managed by LXD, effectively leaking sensitive metadata about the container environment. The vulnerability arises because the API does not properly restrict or validate requests that use wildcard characters in fingerprint parameters, leading to unauthorized information disclosure. The CVSS 4.0 vector (AV:N/AC:L/AT:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N) indicates that the attack can be performed remotely over the network with low complexity, no privileges, and no user interaction required. The impact is limited to information disclosure without direct compromise of data integrity or availability. No patches were linked at the time of publication, but Canonical is expected to release fixes in upcoming versions. No known exploitation in the wild has been reported, but the vulnerability could be leveraged as a reconnaissance step in multi-stage attacks targeting containerized environments.
Potential Impact
For European organizations, this vulnerability poses a risk primarily in terms of information leakage that could facilitate further attacks. By revealing the existence of projects on LXD hosts, attackers gain intelligence that can be used to tailor subsequent exploits or lateral movement strategies. Organizations heavily reliant on containerization and Linux-based infrastructure, such as cloud service providers, financial institutions, and critical infrastructure operators, may find this particularly concerning. Although the vulnerability does not directly compromise data confidentiality or system integrity, the exposure of project metadata can weaken security postures and increase the attack surface. Additionally, the ease of exploitation without authentication means that attackers can perform reconnaissance from remote locations without needing insider access. This could lead to targeted attacks against high-value containerized workloads prevalent in European data centers. The medium severity rating reflects the moderate but non-trivial risk posed by this vulnerability.
Mitigation Recommendations
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.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland
CVE-2025-54290: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in Canonical LXD
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-54290 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) affecting Canonical's LXD container hypervisor software on Linux platforms. The flaw exists in the image export API of LXD versions prior to 6.5 and 5.21.4, where crafted network requests using wildcard fingerprints can be sent without authentication to the API. This allows an attacker to infer the existence of projects managed by LXD, effectively leaking sensitive metadata about the container environment. The vulnerability arises because the API does not properly restrict or validate requests that use wildcard characters in fingerprint parameters, leading to unauthorized information disclosure. The CVSS 4.0 vector (AV:N/AC:L/AT:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N) indicates that the attack can be performed remotely over the network with low complexity, no privileges, and no user interaction required. The impact is limited to information disclosure without direct compromise of data integrity or availability. No patches were linked at the time of publication, but Canonical is expected to release fixes in upcoming versions. No known exploitation in the wild has been reported, but the vulnerability could be leveraged as a reconnaissance step in multi-stage attacks targeting containerized environments.
Potential Impact
For European organizations, this vulnerability poses a risk primarily in terms of information leakage that could facilitate further attacks. By revealing the existence of projects on LXD hosts, attackers gain intelligence that can be used to tailor subsequent exploits or lateral movement strategies. Organizations heavily reliant on containerization and Linux-based infrastructure, such as cloud service providers, financial institutions, and critical infrastructure operators, may find this particularly concerning. Although the vulnerability does not directly compromise data confidentiality or system integrity, the exposure of project metadata can weaken security postures and increase the attack surface. Additionally, the ease of exploitation without authentication means that attackers can perform reconnaissance from remote locations without needing insider access. This could lead to targeted attacks against high-value containerized workloads prevalent in European data centers. The medium severity rating reflects the moderate but non-trivial risk posed by this vulnerability.
Mitigation Recommendations
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.
Affected Countries
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- canonical
- Date Reserved
- 2025-07-18T07:59:07.917Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 68de46967ead30c0938fe4cd
Added to database: 10/2/2025, 9:32:06 AM
Last enriched: 10/9/2025, 10:05:39 AM
Last updated: 1/7/2026, 4:53:33 AM
Views: 88
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-0650: CWE-306 Missing Authentication for Critical Function in OpenFlagr Flagr
CriticalCVE-2025-15474: CWE-770 Allocation of Resources Without Limits or Throttling in AuntyFey AuntyFey Smart Combination Lock
MediumCVE-2025-14468: CWE-352 Cross-Site Request Forgery (CSRF) in mohammed_kaludi AMP for WP – Accelerated Mobile Pages
MediumCVE-2025-9611: CWE-749 Exposed Dangerous Method or Function in Microsoft Playwright
HighCVE-2026-22162
LowActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.