Servers and applications
CVE-2025-54286
CSRF Vulnerability When Using Client Certificate Authentication with the LXD-UI
- Severity
- High 7.5
- Published
- 2 Oct 2025
- Last changed
- 12 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 5.0.5, 5.21.4, 6.5
- Exploit chance
- 0.1% in the next 30 daysHigher than 2% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Only under certain conditions · No login needed · Needs someone to click or open something
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Also known as
- GHSA-p8hw-rfjg-689h
- Sources
- NVD, Project advisories (GitHub)
Description
OIDC authentication uses cookies with the SameSite=Strict attribute, preventing cookies from being sent with requests from other sites. Therefore, CSRF does not occur as long as web services in a Same Site relationship (same eTLD+1) with the origin running LXD-UI are trusted.
However, since the SameSite concept does not apply to client certificates, CSRF protection that doesn't rely on the SameSite attribute is necessary.
Note that when using cross-origin fetch API, client certificates are not sent in no-cors mode due to CORS restrictions (according to the WHATWG Fetch specification(https://fetch.spec.whatwg.org/#credentials), client certificates are treated as credentials), making cross-site attacks using fetch API difficult unless CORS settings are vulnerable. However, since LXD's API parses request bodies as JSON even when Content-Type is text/plain or application/x-www-form-urlencoded, CSRF attacks exploiting HTML form submissions are possible.
Affected software
| Software | Affected versions |
|---|---|
LXDServers and applications · cpe:a:canonical:lxd |
|
LXDServers and applications · github:canonical/lxd |
|
About LXD
container manager for system containers
- GitHub stars
- 4,852GitHub, 15 Nov 2026
- Forks
- 1,074GitHub, 15 Nov 2026
- Latest release
- lxd-6.10.1GitHub, 15 Nov 2026
- Released
- 28 Oct 2026GitHub
- Developer
- Stéphane GraberWikidata
- License
- AGPL-3.0GitHub
- Written in
- GoWikidata
- First released
- 4 Nov 2014Wikidata
- First published on GitHub
- 4 Nov 2014GitHub
Vulnerabilities in LXD
- In our list
- 51
- Published in the last 12 months
- 36
- Critical, last 12 months
- 25
- High, last 12 months
- 5
- Known exploited
- 0
- CVE-2026-112816Authentication bypass through unverified client certificate chainsCritical 10.0 30 Oct 2026
- CVE-2026-86334CLI path traversal when exporting an image from a malicious serverMedium 4.2 25 Sept 2026
- CVE-2026-86335Restricted client can import a private image from another projectMedium 6.3 25 Sept 2026
- CVE-2026-85526Path traversal via btrfs optimized-backup `subvolumes[].path` enables root file/dir manipulationCritical 9.9 25 Sept 2026
- CVE-2026-85185btrfs optimized backup/migration: unvalidated subvolume path enables root arbitrary file delete/write (RCE ceiling)Critical 9.6 25 Sept 2026
- CVE-2026-97335Project restriction bypass for custom volume copy with omitted source typeHigh 7.7 25 Sept 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2025-54286
- CVE.org https://www.cve.org/CVERecord?id=CVE-2025-54286
- GitHub Advisory Database https://github.com/advisories/GHSA-p8hw-rfjg-689h
- github.com https://github.com/canonical/lxd/security/advisories/GHSA-p8hw-rfjg-689h