Skip to content
Fencer Intel
medium 6.5

CVE-2025-54293 json

Path Traversal in LXD Instance Log File Retrieval

published last yr. modified 28d ago also GHSA-472f-vmf2-pr3h , GO-2025-4000 , EUVD-2025-32640

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

Path Traversal in the log file retrieval function in Canonical LXD 5.0 LTS on Linux allows authenticated remote attackers to read arbitrary files on the host system via crafted log file names or symbolic links.

Patch / fix

  • go github.com/canonical/lxd 0.0.0-20250224180022-ec09b24179f3, 5.21.4, 6.5
  • Canonical LXD 5.21.4, 6.5
  • lxd Debian 13 5.0.2+git20231211.1364ae4-9+deb13u1
  • incus Debian 13 6.0.4-2+deb13u1
  • incus Debian 14 6.0.5-1

debian advisories DEBIAN-CVE-2025-54293

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20251105T184115-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2025:15710-1

  • incus Alpine 3.24, Alpine 3.23 6.0.6-r0

alpine advisories ALPINE-CVE-2025-54293

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2025-54293 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/canonical/lxd/security/advisories/GHSA-472f-vmf2-pr3h referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 7.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CNA 4.0 7.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/canonical/lxd
>=4.0, <5.21.4
>=6.0, <6.5
>=0.0.0-20200331193331-03aab09f5b5c, <0.0.0-20250224180022-ec09b24179f3
5.21.4
6.5
0.0.0-20250224180022-ec09b24179f3

Affected products

  • Canonical LXD

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.