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.
CVE-2026-3351
This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(medium)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
March 3, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Aug 6, 2026Non-recursive certificate listing bypasses per-object authorization and leaks all fingerprints · Advisory · canonical/lxd · GitHub
https://github.com/canonical/lxd/security/advisories/GHSA-crmg-9m86-636rlxd/certificates: Return only allowed certificates in non-recursive list
Fix merged in canonical/lxd PR #17738 on 2026-02-24 — awaiting tagged release
https://github.com/canonical/lxd/pull/17738commit d936c90d47cf (canonical/lxd)
Fix landed in canonical/lxd commit d936c90d47cf — awaiting tagged release
https://github.com/canonical/lxd/commit/d936c90d47cf0be1e9757df897f769e9887ebde1Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/canonical/lxd | — | 0.0.0-20260224152359-d936c90d47cf | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 28× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:36 UTCOSV refresh
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 22:04 UTCOSV refresh
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
Show 35 moreShow fewer
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 08:41 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 00:32 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 08:50 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 08:34 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 08:18 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 20:14 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 02:48 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 04:33 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 19:08 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 13:56 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-3351?
When was CVE-2026-3351 disclosed?
Is CVE-2026-3351 actively exploited?
What is the CVSS score of CVE-2026-3351?
How do I remediate CVE-2026-3351?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3351
Is Your Infrastructure Affected by CVE-2026-3351?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.