Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as restricted TLS certificate user
-
DeliverySend PUT/PATCH request to /1.0/certificates/{fingerprint}
-
ExploitOmit Type field validation in doCertificateUpdate
-
ExecutionEscalate privileges to cluster admin
-
ImpactGain high-impact access across system
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V4 - API and Web Service Object attribute protection
|
| Exploitation Conditions | Canonical LXD 4.12–6.7 with TLS certificate authentication enabled. Attacker must be authenticated as a restricted TLS certificate user and send PUT/PATCH requests to /1.0/certificates/{fingerprint} endpoint to escalate to cluster admin privileges. |
| Impact | High-impact privilege escalation in LXD affecting versions 4.12-6.7. Requires authenticated access (high privilege), but achieves cluster admin escalation with full confidentiality, integrity, and availability compromise across infrastructure. Patch availability reduces urgency. EPSS and KEV status unknown; real-world priority depends on LXD exposure in Kubernetes/containerized environments and patch adoption rates. |
| Exploit ScenarioDerived | Authenticated cluster user with restricted TLS certificate permissions sends PUT/PATCH request to /1.0/certificates/{fingerprint}, omitting Type field validation in doCertificateUpdate. Attacker modifies certificate metadata to escalate to cluster admin. No public exploit code identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 09, 2026
Privilege escalation in Canonical LXD 4.12 through 6.7 enables remote authenticated restricted TLS certificate users to gain cluster admin privileges. Exploitation requires high-privilege authentication (PR:H) but no user interaction. The vulnerability stems from missing Type field validation in doCertificateUpdate function when processing PUT/PATCH requests to the certificates API endpoint. Attack scope is changed (S:C), allowing attackers to break containment and achieve full cluster compromise with high impact to confidentiality, integrity, and availability. No public exploit identified at time of analysis.
RemediationAI
Vendor-released patch: upstream fix available via GitHub pull request (https://github.com/canonical/lxd/pull/17936); released patched version not independently confirmed at time of analysis. Organizations should monitor Canonical's official security advisory (https://github.com/canonical/lxd/security/advisories/GHSA-c3h3-89qf-jqm5) for release announcements and apply updates immediately upon availability. As an interim mitigation, restrict network access to the LXD API endpoint /1.0/certificates/* to trusted networks only, implement additional authentication layers for certificate management operations, audit existing TLS certificate users for appropriate privilege levels, and revoke restricted certificates if cluster admin escalation risk is unacceptable. Enable comprehensive API request logging to detect unauthorized certificate modification attempts.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in go, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The doCertificateUpdate function in lxd/certificates.go fails to validate the Type field during certificate modification operations. This CWE-915 (improperly controlled modification of dynamically-determined object attributes) flaw allows authenticated restricted certificate users to manipulate certificate properties via PUT/PATCH to /1.0/certificates/{fingerprint}, bypassing intended access controls and elevating to cluster administrator role. Network-accessible (AV:N), low complexity (AC:L), requiring high privileges (PR:H).
Know when Lxd gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Primary rating from Vendor (canonical).
CVSS VectorVendor: canonical
Lifecycle Timeline
2DescriptionCVE.org
In Canonical LXD versions 4.12 through 6.7, the doCertificateUpdate function in lxd/certificates.go does not validate the Type field when handling PUT/PATCH requests to /1.0/certificates/{fingerprint} for restricted TLS certificate users, allowing a remote authenticated attacker to escalate privileges to cluster admin.
Executive ViewAI
CVE-2026-34179 is a critical privilege escalation flaw in Canonical LXD versions 4.12-6.7 that allows authenticated users with restricted TLS certificate permissions to escalate to cluster administrator privileges, potentially compromising all container infrastructure and data within the LXD cluster. Organizations running affected LXD versions must prioritize patching to prevent lateral movement and full infrastructure takeover by adversaries with initial certificate-level access.
Apply vendor patch. Until patching is complete: restrict TLS certificate issuance to essential use cases only; implement network segmentation to limit which users/systems can authenticate to LXD cluster endpoints; monitor PUT/PATCH requests to the certificates API endpoint for anomalous activity; disable non-essential certificate-based authentication methods where operationally feasible.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Related Vulnerabilities in Canonical LXD Security Bypass
View all 3Cross-site request forgery in the LXD-UI component of Canonical LXD 5.0 before 5.0.5, 5.1 before 5.21.4, and 6.0 before
Privilege escalation in Canonical LXD's operations API (LXD before 6.5 and LXD 5.21 before 5.21.4) allows an authenticat
Authenticated remote attackers with access to the Canonical LXD instance log retrieval or deletion endpoints can read ar
Server-side template injection in Canonical LXD's instance snapshot naming feature lets an authenticated user who can mo
Unauthenticated project enumeration in Canonical LXD 5.21.x before 5.21.4 and 6.x before 6.5 lets remote attackers deter
Unauthenticated remote attackers can confirm the existence of LXD projects on Canonical LXD by comparing HTTP status cod
Privilege escalation to host root in Canonical LXD occurs when the container manager unpacks crafted image or backup arc
Host root code execution in Canonical LXD arises from a path-traversal flaw in instance template processing, letting an
Arbitrary host file read and write in Canonical LXD occurs because the image import/unpack routine does not verify wheth
Canonical LXD's NVIDIA GPU passthrough configuration handler fails to sanitize newline characters in user-supplied `nvid
Path traversal in Canonical's LXD container and VM manager allows a user with backup import/restore privileges to write
Authorization bypass in Canonical LXD (6.0 before 6.10, 5.21.x before 5.21.6, 5.0.x before 5.0.8) lets an authenticated
EUVD-2026-20876
GHSA-c3h3-89qf-jqm5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB