Project existence disclosure in LXD images API
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
cve-program · CVE-2025-54291
PublishedInformation 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.
- Source published
- 2 Oct 2025 09:25:42 UTC
- Source modified
- 2 Oct 2025 17:29:54 UTC
- Observed here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 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
euvd · EUVD-2025-32641
PublishedInformation 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.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Oct 2, 2025, 9:25:42 AM
dateUpdated: Oct 2, 2025, 5:29:54 PM
1 related source bulletins · separate from aliases
openSUSE-SU-2025:15710-1: govulncheck-vulndb-0.0.20251105T184115-1.1 on GA media
CVE-2016-11063 · CVE-2016-11066 · CVE-2016-11067 · CVE-2016-11068 · CVE-2016-11069 · CVE-2016-11070 · CVE-2016-11071 · CVE-2016-11072 · CVE-2016-11073 · CVE-2016-11074 · CVE-2016-11075 · CVE-2016-11076 · CVE-2016-11077 · CVE-2016-11078 · CVE-2016-11079 · CVE-2016-11080 · CVE-2016-11081 · CVE-2016-11082 · CVE-2016-11083 · CVE-2016-11084 · CVE-2017-18872 · CVE-2023-32199 · CVE-2024-58269 · CVE-2025-10545 · CVE-2025-10678 · CVE-2025-10954 · CVE-2025-11374 · CVE-2025-11375 · CVE-2025-11579 · CVE-2025-11621 · CVE-2025-12044 · CVE-2025-26625 · CVE-2025-27093 · CVE-2025-41410 · CVE-2025-41443 · CVE-2025-54286 · CVE-2025-54287 · CVE-2025-54288 · CVE-2025-54289 · CVE-2025-54290 · CVE-2025-54291 · CVE-2025-54293 · CVE-2025-54469 · CVE-2025-54470 · CVE-2025-54471 · CVE-2025-54499 · CVE-2025-58073 · CVE-2025-58075 · CVE-2025-58356 · CVE-2025-59043 · CVE-2025-59048 · CVE-2025-59530 · CVE-2025-59836 · CVE-2025-59937 · CVE-2025-61141 · CVE-2025-61524 · CVE-2025-61581 · CVE-2025-61688 · CVE-2025-62156 · CVE-2025-62157 · CVE-2025-62375 · CVE-2025-62506 · CVE-2025-62513 · CVE-2025-62705 · CVE-2025-62714 · CVE-2025-62725 · CVE-2025-62820 · CVE-2025-64101 · CVE-2025-64102 · CVE-2025-64103
- Source published
- Oct 2, 2025, 9:25:42 AM (timezone not stated)
- Source modified
- Oct 2, 2025, 5:29:54 PM (timezone not stated)
- Observed here
- 9 Nov 2026 03:10:04 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.
EUVD CVSS 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
nvd · CVE-2025-54291
PublishedInformation 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.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-209
Original publisher date fields
published: 2025-10-02T10:15:39.387
lastModified: 2026-10-12T15:10:00.207
1 source CPE criteria · context only
- cpe:2.3:a:canonical:lxd:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 2 Oct 2025 10:15:39 UTC
- Source modified
- 12 Oct 2026 15:10:00 UTC
- Observed here
- 25 Oct 2026 02:25:06 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 4.0 · [email protected] · Secondary · 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
CVSS 3.1 · [email protected] · Primary · 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
osv · GHSA-xch9-h8qw-85c7
Published### Impact The LXD /1.0/images endpoint is implemented as an AllowUntrusted API that requires no authentication, making it accessible to users without accounts. This API allows determining project existence through differences in HTTP status codes when accessed with the project parameter. https://github.com/canonical/lxd/blob/43d5189564d27f6161b430ed258c8b56603c2759/lxd/images.go#L63-L69 This configuration allows access without authentication: https://github.com/canonical/lxd/blob/43d5189564d27f6161b430ed258c8b56603c2759/lxd/daemon.go#L924-L926 This API returns a 404 error when accessing existing projects and a 403 error when accessing non-existent projects, allowing confirmation of project existence through this difference. The problematic implementation is shown below. First, in the error handling implementation of the imagesGet function below, project existence is checked within the `projectutils.ImageProject` function, and the err returned by the `ImageProject` function is directly returned to the user. https://github.com/canonical/lxd/blob/43d5189564d27f6161b430ed258c8b56603c2759/lxd/i mages.go#L1781-L1788 When the project doesn't exist, the error is 404 (http.StatusNotFound), which is returned to the user: https://github.com/canonical/lxd/blob/43d5189564d27f6161b430ed258c8b56603c2759/lxd/db/cluster/projects.mapper.go#L237-L239 On the other hand, when the project exists but the user lacks viewing permissions, the imagesGet function returns 403 (response.Forbidden): https://github.com/canonical/lxd/blob/43d5189564d27f6161b430ed258c8b56603c2759/lxd/images.go#L1796-L1799 ### Reproduction Steps 1. Send the following request without authentication to a non-existent project: ``` curl -k "https://lxd-host:8443/1.0/images?project=XXX-project" ``` Response: ```json {"type":"error","status":"","status_code":0,"operation":"","error_code":404,"error":"fetch project: Project not found","metadata":null} ``` 2. Send a request without authentication to an existing project (if a public project exists, it will be included in the response): ``` curl -k "https://lxd-host:8443/1.0/images?project=exist-project" ``` Reponse: ``` {"type":"error","status":"","status_code":0,"operation":"","error_code":403,"error":"Untrusted callers may only access public images in the default project","metadata":null} ``` ### 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 othervulnerabilities. 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 the error handling in the imagesGet function to return consistent responses regardless of project existence. Specifically, when an error occurs during project existence verification, the implementation should be changed to always return a 403 (Untrusted callers may only access public images in the default project) error to unauthenticated users. This ensures that the same error response is returned for both existing and non-existing projects, preventing determination of project existence. ### 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.
- Source published
- 2 Oct 2025 21:15:46 UTC
- Source modified
- 10 Sep 2026 03:50:30 UTC
- Observed here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CVSS_V4 · 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
Publisher rating · MODERATE
osv · GO-2025-4005
PublishedCanonical LXD Project Existence Determination Through Error Handling in Image Get Function in github.com/canonical/lxd
- Source published
- 5 Nov 2025 18:41:07 UTC
- Source modified
- 5 Nov 2025 19:57:39 UTC
- Observed here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.