CVE-2025-54286: CSRF Vulnerability When Using Client Certificate Authentication with the LXD-UI
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. Special conditions such as timing or configuration are required.
- Fixed version: Canonical LXD 5.0.5, 5.21.4, 6.5.
Low priority for now. Upgrade to Canonical LXD 5.0.5, 5.21.4, 6.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Cross-Site Request Forgery (CSRF) in LXD-UI in Canonical LXD versions >= 5.0 on Linux allows an attacker to create and start container instances without user consent via crafted HTML form submissions exploiting client certificate authentication.
- Published
- Oct 2, 2025
- Updated
- Oct 12, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-352
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · canonical
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical lxd5.0.0 and later · before 5.0.5
- canonical lxd5.21.0 and later · before 5.21.4
- canonical lxd6.1 and later · before 6.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (canonical). Independent of NVD's CPE analysis and usually ahead of it.
Canonical LXD
- 5.0 and later · before 5.0.5affected · semver
- 5.21 and later · before 5.21.4affected · semver
- 6.0 and later · before 6.5affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.23 | incus | before 6.0.6-r0 | 6.0.6-r0 |
| Debian:12 | lxd | from 0 | — |
| Debian:12 | lxd | before 5.0.2-5+deb12u1 | 5.0.2-5+deb12u1 |
| Debian:13 | incus | before 6.0.4-2+deb13u1 | 6.0.4-2+deb13u1 |
| Debian:13 | lxd | before 5.0.2+git20231211.1364ae4-9+deb13u1 | 5.0.2+git20231211.1364ae4-9+deb13u1 |
| Debian:14 | incus | before 6.0.5-1 | 6.0.5-1 |
| Go | github.com/canonical/lxd | from 0 | — |
| Go | github.com/canonical/lxd | from 0.0.0-20220401034332-1e1349e3cbf3 · before 0.0.0-20250827065555-0494f5d47e41 | 0.0.0-20250827065555-0494f5d47e41 |
| Go | github.com/canonical/lxd | from 5.0 · before 5.0.5 | 5.0.5 |
| Go | github.com/canonical/lxd | from 5.1 · before 5.21.4 | 5.21.4 |
| Go | github.com/canonical/lxd | from 6.0 · before 6.5 | 6.5 |
Same product
canonical: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-112816Improper certificate validation in the HTTPS listener in LXD40Plan
- CVE-2026-87799Arbitrary file write on LXD host via symlink in migration stream39Monitor
- CVE-2026-85526Path traversal via Btrfs optimized-backup subvolumes[].path enables root file/dir manipulation in LXD39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-6156Dec 5, 2024 · Mark Laing discovered that LXD's PKI mode, until version 5.21.2, could be bypassed if the client's certificate was present in the trust stor15Monitor
- ← EarlierCVE-2024-6219Dec 5, 2024 · Mark Laing discovered in LXD's PKI mode, until version 5.21.1, that a restricted certificate could be added to the trust store with its rest15Monitor
- Later →CVE-2025-54287Oct 2, 2025 · Arbitrary File Read via Template Injection in Snapshot Patterns28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Canonical LXD | 5.0.5 | Vendor (CNA) |
| Canonical LXD | 5.21.4 | Vendor (CNA) |
| Canonical LXD | 6.5 | Vendor (CNA) |
| alpine:incus | 6.0.6-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:incus | 6.0.4-2+deb13u1 · Debian:13 | Package registry (OSV) |
| debian:lxd | 5.0.2+git20231211.1364ae4-9+deb13u1 · Debian:13 | Package registry (OSV) |
| Go:github.com/canonical/lxd | 0.0.0-20250827065555-0494f5d47e41 | Package registry (OSV) |
| Go:github.com/canonical/lxd | 5.0.5 | Package registry (OSV) |
| Go:github.com/canonical/lxd | 5.21.4 | Package registry (OSV) |
| Go:github.com/canonical/lxd | 6.5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)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
nvd-secondary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →