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

Advisory record · `GHSA-crmg-9m86-636r`

- **Identifiers:** `GHSA-crmg-9m86-636r` · `CVE-2026-3351` · `GO-2026-4595`
- **State:** Confirmed
- **Severity:** CVSS 2.1 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 4 Mar 2026
- **Updated:** 23 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Mar 2026, 20:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/canonical/lxd` (Go): affected `<0.0.0-20260224152359-d936c90d47cf`; fixed in `0.0.0-20260224152359-d936c90d47cf`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The non-recursive form of the certificate listing in github.com/canonical/lxd, before commit d936c90d47cf (version 0.0.0-20260224152359-d936c90d47cf), returns URLs containing fingerprints for every trusted certificate without applying the per-certificate view permission check. Any authenticated trusted user, including restricted non-admin users, can list all certificate fingerprints. The fix is to upgrade to 0.0.0-20260224152359-d936c90d47cf; no workaround is given.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 2.1 Low, CVSS 4.0: `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/E:P`, from CNA (canonical)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 4th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-crmg-9m86-636r)

## Sources

- [GitHub Advisory Database: GHSA-crmg-9m86-636r](https://github.com/advisories/GHSA-crmg-9m86-636r)
- [OSV: GHSA-crmg-9m86-636r](https://osv.dev/vulnerability/GHSA-crmg-9m86-636r)
- <https://github.com/canonical/lxd/security/advisories/GHSA-crmg-9m86-636r>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-3351>
- <https://github.com/canonical/lxd/pull/17738>
- <https://github.com/canonical/lxd/commit/d936c90d47cf0be1e9757df897f769e9887ebde1>
- <https://github.com/canonical/lxd>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-crmg-9m86-636r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-crmg-9m86-636r/>. Everything for agents: <https://agentprime.io/llms.txt>.
