Lxd vulnerabilitiesRanked by how likely they are to be used.
Lxd is made by Canonical. We track 12 published vulnerabilities in it, across 170 versions. None of them is on the list of flaws known to be exploited today. If you run Lxd, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Lxd vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Lxd's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Lxd flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.4%CVE-2025-54291Medium
Information disclosure in images API in Canonical LXD before 6.5 and 5.21.4 on all platforms allows unauthenticated remote attackers to determine project existence via differing HTTP status code responses.
- 0.4%CVE-2025-54287Medium
Template Injection in instance snapshot creation component in Canonical LXD (>= 4.0) allows an attacker with instance configuration permissions to read arbitrary files on the host system via specially crafted...
- 0.4%CVE-2025-54288Medium
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...
- 0.3%CVE-2016-1582Medium
LXD before 2.0.2 does not properly set permissions when switching an unprivileged container into privileged mode, which allows local users to access arbitrary world readable paths in the container directory via...
- 0.3%CVE-2025-54290Medium
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.
- 0.3%CVE-2016-1581Medium
LXD before 2.0.2 uses world-readable permissions for /var/lib/lxd/zfs.img when setting up a loop based ZFS pool, which allows local users to copy and read data from arbitrary containers via unspecified vectors.
- 0.3%CVE-2023-48733Medium
An insecure default to allow UEFI Shell in EDK2 was left enabled in Ubuntu's EDK2.
- 0.2%CVE-2023-49721Medium
An insecure default to allow UEFI Shell in EDK2 was left enabled in LXD.
- 0.2%CVE-2025-54289High
Privilege Escalation in operations API in Canonical LXD <6.5 on multiple platforms allows attacker with read permissions to hijack terminal or console sessions and execute arbitrary commands via WebSocket connection...
- 0.2%
Mark Laing discovered that LXD's PKI mode, until version 5.21.2, could be bypassed if the client's certificate was present in the trust store.
Running Lxd? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Information disclosure in images API in Canonical LXD before 6.5 and 5.21.4 on all platforms allows unauthenticated remote attackers to determine project existence via differing HTTP status code responses.
- Matched to
- Lxd on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 12 published vulnerabilities listed under the name Lxd, across 170 versions.
None of Lxd's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Lxd. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.