# CVE-2026-3351: Authorization Bypass in LXD GET /1.0/certificates Endpoint

> An authenticated restricted user can bypass authorization to enumerate all trusted certificate fingerprints in LXD.

- **Severity:** Low 2.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Mar 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-crmg-9m86-636r, GO-2026-4595, UBUNTU-CVE-2026-3351

## What is CVE-2026-3351?

CVE-2026-3351 is a low-severity missing authorization vulnerability in Canonical lxd, published on 3 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper authorization in the API endpoint GET /1.0/certificates in Canonical LXD 6.6 on Linux allows an authenticated, restricted user to enumerate all certificate fingerprints trusted by the lxd server.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-3351?

3 open source packages ship an affected version, including github.com/canonical/lxd. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/canonical/lxd` | Go | All versions | None |
| `github.com/canonical/lxd` | Go | All versions | 0.0.0-20260224152359-d936c90d47cf |
| `github.com/canonical/lxd` | Go | All versions | 0.0.0-20260224152359-d936c90d47cf |

Products: Canonical Lxd.

## How do I fix CVE-2026-3351?

Upgrade github.com/canonical/lxd to 0.0.0-20260224152359-d936c90d47cf or later.

## Is CVE-2026-3351 being exploited?

There is no known exploitation of CVE-2026-3351 in the wild and no public exploit code.

## Other vulnerabilities in Canonical lxd

- [CVE-2026-66897](https://insights.sbomify.com/CVE-2026-66897/): Instance template path traversal allows arbitrary host file write as root (critical 9.9)
- [CVE-2026-62420](https://insights.sbomify.com/CVE-2026-62420/): Cross-project cluster migration bypasses project restrictions via cluster notification flag (critical 9.9)
- [CVE-2026-63293](https://insights.sbomify.com/CVE-2026-63293/): Arbitrary File Read/Write: metadata.yaml symlink in image allows host filesystem access as root (critical 9.9)
- [CVE-2026-63294](https://insights.sbomify.com/CVE-2026-63294/): Root RCE via image backup.yaml symlink (critical 9.9)
- [CVE-2026-63296](https://insights.sbomify.com/CVE-2026-63296/): Project restriction bypass via instance migration config override (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3351 and fix it if it is affected.

What it is: CVE-2026-3351 is a low-severity missing authorization vulnerability in Canonical lxd, published on 3 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3351 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/canonical/lxd (Go): affected all versions; no fix listed
- github.com/canonical/lxd (Go): affected all versions; fixed in 0.0.0-20260224152359-d936c90d47cf
- github.com/canonical/lxd (Go): affected all versions; fixed in 0.0.0-20260224152359-d936c90d47cf

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3351/ (Markdown: https://insights.sbomify.com/CVE-2026-3351/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3351
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3351
- OSV: https://osv.dev/vulnerability/CVE-2026-3351

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3351/
Summaries are generated and may contain mistakes; the official description above is the record.