CVSS 4.0
7.1 highCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NHigh (7.1) in canonical lxd. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/canonical/lxd 0.0.0-20250224180022-ec09b24179f3, 5.21.4, 6.5.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:Ngithub.com/canonical/lxd (Go): fixed in 5.21.4, 6.5, 0.0.0-20250224180022-ec09b24179f3Explain CVE-2025-54293 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-54293?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-54293?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-54293 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Canonical LXD | from 6.0 before 6.5 |
| Canonical LXD | from 5.21 before 5.21.4 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-472f-vmf2-pr3h | Go | github.com/canonical/lxd | >=4.0 <5.21.4 | 5.21.4 |
| GHSA-472f-vmf2-pr3h | Go | github.com/canonical/lxd | >=6.0 <6.5 | 6.5 |
| GHSA-472f-vmf2-pr3h | Go | github.com/canonical/lxd | >=0.0.0-20200331193331-03aab09f5b5c <0.0.0-20250224180022-ec09b24179f3 | 0.0.0-20250224180022-ec09b24179f3 |
| GO-2025-4000 | Go | github.com/canonical/lxd | >=0.0.0-20200331193331-03aab09f5b5c <0.0.0-20250224180022-ec09b24179f3 | 0.0.0-20250224180022-ec09b24179f3 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | lxd | no fix listed | DEBIAN-CVE-2025-54293 DSA-6028-1 |
| Debian | 13 | incus | 6.0.4-2+deb13u1 | DEBIAN-CVE-2025-54293 DSA-6027-1 |
| Debian | 13 | lxd | 5.0.2+git20231211.1364ae4-9+deb13u1 | DEBIAN-CVE-2025-54293 DSA-6028-1 |
| Debian | 14 | incus | 6.0.5-1 | DEBIAN-CVE-2025-54293 |
| Ubuntu | 20.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS | lxd | no fix listed | UBUNTU-CVE-2025-54293 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
| openSUSE | Tumbleweed | govulncheck-vulndb | 0.0.20251105T184115-1.1 | openSUSE-SU-2025:15710-1 |
| Alpine | v3.23, v3.24 | incus | 6.0.6-r0 | ALPINE-CVE-2025-54293 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.