lxd's non-recursive certificate listing bypasses per-object authorization and leaks all fingerprints

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N · score source

EPSS

• CVE-2026-3351: 0.15% estimated exploitation activity in the next 30 days; percentile 4.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The GET /1.0/certificates endpoint (non-recursive mode) returns URLs containing fingerprints for all certificates in the trust store, bypassing the per-object canview authorization check that is correctly applied in the recursive path. Any authenticated identity — including restricted, non-admin users — can enumerate all certificate fingerprints, exposing the full set of trusted identities in the LXD deployment. Affected Component - lxd/certificates.go — certificatesGet (lines 185–192) — Non-recursive code path returns unfiltered certificate list. CWE - CWE-862: Missing Authorization Description Core vulnerability: missing permission filter in non-recursive listing path The certificatesGet handler obtains a permission checker at line 143 and correctly applies it when building the recursive response (lines 163-176). However, the non-recursive code path at lines 185-192 creates a fresh loop over the unfiltered baseCerts slice, completely bypassing the authorization check:…

Published by the source

4 Mar 2026, 20:18 UTC

Last modified by the source

4 Mar 2026, 20:18 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-crmg-9m86-636r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-3351

Advisory: lxd's non-recursive certificate listing bypasses per-object authorization and leaks all fingerprints
IDs: CVE-2026-3351, GHSA-crmg-9m86-636r
Record: https://patchnext.com/advisories/cve-2026-3351 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/canonical/lxd 0.0.0-20260224152359-d936c90d47cf. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/canonical/lxd: affected < 0.0.0-20260224152359-d936c90d47cf; fixed in 0.0.0-20260224152359-d936c90d47cf

## Suggested inspection (read-only)
- Go github.com/canonical/lxd: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/canonical/lxd.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-crmg-9m86-636r (GitHub-reviewed advisory GHSA-crmg-9m86-636r lists affected ranges: Go github.com/canonical/lxd >=0 <0.0.0-20260224152359-d936c90d47cf)

Commands are suggestions: review each one before running it.