CVE-2025-54288: Canonical LXD · Authentication Bypass by Spoofing
Affects Canonical LXDSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Canonical LXD | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-54288, European organizations should implement strict privilege management to minimize root access within containers, employing the principle of least privilege. Container runtime security policies should be enforced to restrict process name modifications and detect anomalous command-line arguments indicative of spoofing attempts. Employing container security tools that monitor inter-container communications and metadata access can help identify suspicious behavior. Network segmentation and strong access controls between containers can limit the blast radius of a compromised container. Organizations should also stay vigilant for Canonical's security advisories and apply patches promptly once available. Additionally, adopting runtime security solutions that provide behavioral analytics and anomaly detection can help detect exploitation attempts early. Regular audits of container configurations and metadata access logs will aid in identifying unauthorized access. Finally, consider isolating sensitive workloads in dedicated container hosts or using hardware-assisted isolation technologies to reduce risk.
Description
Information Spoofing in devLXD Server in Canonical LXD versions 4.0 and above on Linux container platforms allows attackers with root privileges within any container to impersonate other containers and obtain their metadata, configuration, and device information via spoofed process names in the command line.