Skip to content
Fencer Intel
medium 5.3

CVE-2025-54291 json

Project existence disclosure in LXD images API

published last yr. modified 28d ago also GHSA-xch9-h8qw-85c7 , GO-2025-4005 , EUVD-2025-32641

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

Summary

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.

Patch / fix

  • go github.com/canonical/lxd 0.0.0-20250827065555-0494f5d47e41, 5.21.4, 6.5
  • Canonical LXD 5.21.4, 6.5
  • incus Debian 13 6.0.4-2+deb13u1
  • incus Debian 14 6.0.5-1

debian advisories DEBIAN-CVE-2025-54291

  • 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-54291

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-54291 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.39% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/canonical/lxd/security/advisories/GHSA-xch9-h8qw-85c7 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 6.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
CNA 4.0 6.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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-20250827065555-0494f5d47e41
5.21.4
6.5
0.0.0-20250827065555-0494f5d47e41

Affected products

  • Canonical LXD

Classification

Weakness
  • CWE-209 Generation of Error Message Containing Sensitive Information

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.