CVE-2025-54290: Canonical LXD Project Existence Determination Through Error Handling in Image Export Function
Impact In LXD's images export API (/1.0/images/{fingerprint}/export), implementation differences in error handling allow determining project existence without authentication. Specifically, in the following code, errors when multiple images match are directly returned to users as API responses: https://github.com/canonical/lxd/blob/43d5189564d27f6161b430ed258c8b56603c2759/lxd/db/images.go#L239-L246 While fingerprints…
Published Oct 2, 2025 · Updated Nov 5, 2025
Affected packages
github.com/canonical/lxd
- Ecosystem
- Go
- Affected
- >= 4.0, < 5.21.4
- Fixed in
- 5.21.4
- Check
go list -m github.com/canonical/lxd
github.com/canonical/lxd
- Ecosystem
- Go
- Affected
- >= 6.0, < 6.5
- Fixed in
- 6.5
- Check
go list -m github.com/canonical/lxd
github.com/canonical/lxd
- Ecosystem
- Go
- Affected
- >= 0.0.0-20200331193331-03aab09f5b5c, < 0.0.0-20250827065555-0494f5d47e41
- Fixed in
- 0.0.0-20250827065555-0494f5d47e41
- Check
go list -m github.com/canonical/lxd
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
In LXD's images export API (/1.0/images/{fingerprint}/export), implementation differences in error handling allow determining project existence without authentication.
Specifically, in the following code, errors when multiple images match are directly returned to users as API responses:
https://github.com/canonical/lxd/blob/43d5189564d27f6161b430ed258c8b56603c2759/lxd/db/images.go#L239-L246
While fingerprints generally don't duplicate, this functionality uses fingerprints with LIKE clauses, allowing prefix specification. Therefore, using LIKE wildcards such as % will match multiple images if multiple images exist in the project.
https://github.com/canonical/lxd/blob/43d5189564d27f6161b430ed258c8b56603c2759/lxd/db/images.go#L277-L286
In the above implementation, multiple matches result in a 500 error, but if the project itself doesn't exist, there are 0 matches and a 404 is returned.
- When project exists and multiple images match: HTTP 500 error "More than one image matches"
- When project doesn't exist: HTTP 404 error "not found"
This behavioural difference allows attackers to confirm project existence without authentication.
Reproduction Steps
- Send a request with a pattern matching multiple entries to an existing project (default):
curl -k 'https://lxd-host:8443/1.0/images/%25/export?project=default&secret=x'Response:
{"type":"error","status":"","status_code":0,"operation":"","error_code":500,"error":"More than one image matches","metadata":null}- Send a same request to a non-existent project (not-exist):
curl -k 'https://lxd-host:8443/1.0/images/%25/export?project=not-exist&secret=x'Response:
{"type":"error","status":"","status_code":0,"operation":"","error_code":404,"error":"not found","metadata":null}This difference allows enumerating existing projects in the system by brute-forcing(dictionary attack) project names.
Note that %25 is the URL encoding of %, which works as a wildcard matching all characters in SQL LIKE clauses. This is used to intentionally create requests matching multiple images to trigger a 500 error.
Additionally, the secret parameter is added to include non-public images in the search, increasing the possibility of multiple matches.
https://github.com/canonical/lxd/blob/43d5189564d27f6161b430ed258c8b56603c2759/lxd/images.go#L4211-L4230
Risk
The attack requires only network access to the LXD API endpoint, with no authentication needed.
The attack allows confirming the existence of projects within the LXD system by exploiting differences in HTTP status codes. This could potentially increase the exploitability of other vulnerabilities. Additionally, since project IDs often use meaningful names set by users, this could lead to leakage of unpublished product information.
However, resource information within projects cannot be obtained, limiting the impact to existence confirmation only.
Countermeasures
It is recommended to modify error handling in the images export API (/1.0/images/{fingerprint}/export) to return consistent responses regardless of project existence.
Specifically, return 404 even when errors occur during project existence verification. This ensures the same error response is returned for both existing and non-existing projects, preventing determination of project existence.
Additionally, if there are no specification(compatibility) issues, allowing only exact fingerprint matches in unauthenticated states and disabling prefix matching can prevent unexpected errors from occurring.
Patches
| LXD Series | Status | | 6 | Fixed in LXD 6.5 | | 5.21 | Fixed in LXD 5.21.4 | | 5.0 | Ignored - Not critical | | 4.0 | Ignored - EOL and not critical |
References
Reported by GMO Flatt Security Inc.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-28385
LXD: SSRF via image import from URL allows internal network probing by authenticated users
medium5.0Nov 6, 2026CVE-2026-9639
LXD has CreateCustomVolumeFromBackup nil-pointer dereference on volumes[0].snapshots[*].expires_at
medium6.5Nov 6, 2026GHSA-47w9-6r3f-938g
LXD has restricted project bypass leading to arbitrary command execution
critical9.9Nov 6, 2026GHSA-7mr3-28h5-m5vx
LXD has project restriction bypass for custom volume copy across projects
high7.7Nov 6, 2026GHSA-9j25-mm2h-2f76
LXD has arbitrary file write on host via `exec-output` symlink in crafted image
critical9.9Nov 6, 2026GHSA-fmc8-p6q7-75cc
LXD has argument injection in backup compression algorithm leading to AFW and ACE
critical9.9Nov 6, 2026
