Cross-container data disclosure via process-name spoofing
Published Oct 2, 2025 · Updated Oct 2, 2025
Information disclosure in Canonical LXD 5.21 before 5.21.4 and 6.0 before 6.5 allows attackers to read other containers' data. The devLXD findContainerForPID function trusts a spoofable [lxc monitor] process name before validating the caller's PID namespace, selecting an attacker-named container. Root access inside any container permits reads of another container's metadata, user and cloud-init configuration, and device details through the local devLXD socket.
Summary
What happened
Information disclosure in Canonical LXD 5.21 before 5.21.4 and 6.0 before 6.5 allows attackers to read other containers' data. The devLXD findContainerForPID function trusts a spoofable [lxc monitor] process name before validating the caller's PID namespace, selecting an attacker-named container. Root access inside any container permits reads of another container's metadata, user and cloud-init configuration, and device details through the local devLXD socket.
The record
- CVE
- CVE-2025-54288
- Published
- Oct 2, 2025
- Updated
- Oct 2, 2025
- Vendor
- Canonical
- Product
- LXD
- Classifications
- CWE-290, T1036
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Oct 2, 2025CVE publishedPublication date reported by the CVE source.
- Oct 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.21 <5.21.4
- Affected versionversion=6.0 <6.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Canonical devLXD cmdline-spoofing reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo