Advisory record · GHSA-p8hw-rfjg-689h

Canonical LXD CSRF Vulnerability When Using Client Certificate Authentication with the LXD-UI

CVSS 7.5 HighEPSS 0.0013 · 2nd percentile

Published by the GitHub Advisory Database at 2 Oct 2025, 21:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/canonical/lxdGo>=5.0, <5.0.5 || >=5.1, <5.21.4 || >=6.0, <6.5 || >=0.0.0-20220401034332-1e1349e3cbf3, <0.0.0-20250827065555-0494f5d47e415.0.5, 5.21.4, 6.5, 0.0.0-20250827065555-0494f5d47e41
Identifiers
GHSA-p8hw-rfjg-689h · CVE-2025-54286 · GO-2025-4003
Weakness (CWE)
CWE-352
Published
2 Oct 2025
Updated
10 Sept 2026

Machine-written summary

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

Canonical LXD (github.com/canonical/lxd) versions from 0.0.0-20220401034332-1e1349e3cbf3 up to, but not including, 0.0.0-20250827065555-0494f5d47e41, and 5.0 before 5.0.5, 5.1 before 5.21.4, and 6.0 before 6.5 are affected. An attacker who lures a logged-in user, authenticated with a client certificate, to a malicious website can use a cross-site form submission to make the API create and start instances, and possibly run commands in containers. Upgrade to 6.5, 5.21.4, 5.0.5, or 0.0.0-20250827065555-0494f5d47e41 or later.

Written 1 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

ScoreRatingCVSSVectorSource
7.5 High 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L CNA (canonical)
  • CISA KEV Not listed.
  • EPSS 0.0013, the 2nd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

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.