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

Advisory record · `GHSA-p8hw-rfjg-689h`

- **Identifiers:** `GHSA-p8hw-rfjg-689h` · `CVE-2025-54286` · `GO-2025-4003`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 2 Oct 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/canonical/lxd` (Go): affected `>=5.0, <5.0.5 || >=5.1, <5.21.4 || >=6.0, <6.5 || >=0.0.0-20220401034332-1e1349e3cbf3, <0.0.0-20250827065555-0494f5d47e41`; fixed in `5.0.5`, `5.21.4`, `6.5`, `0.0.0-20250827065555-0494f5d47e41`

## 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

- 7.5 High, CVSS 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`, from 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

- 31 Oct 2026, 14:14 UTC: First seen by agentprime
- 31 Oct 2026, 14:14 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-p8hw-rfjg-689h)

## Sources

- [GitHub Advisory Database: GHSA-p8hw-rfjg-689h](https://github.com/advisories/GHSA-p8hw-rfjg-689h)
- [OSV: GHSA-p8hw-rfjg-689h](https://osv.dev/vulnerability/GHSA-p8hw-rfjg-689h)
- <https://github.com/canonical/lxd/security/advisories/GHSA-p8hw-rfjg-689h>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-54286>
- <https://github.com/canonical/lxd>
- <https://pkg.go.dev/vuln/GO-2025-4003>

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-p8hw-rfjg-689h>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-p8hw-rfjg-689h/>. Everything for agents: <https://agentprime.io/llms.txt>.