Skip to main content

Lxd CVE-2026-34179

| EUVDEUVD-2026-20876 CRITICAL
Improperly Controlled Modification of Dynamically-Determined Object Attributes (CWE-915)
2026-04-09 canonical GHSA-c3h3-89qf-jqm5
9.1
CVSS 3.1 · Vendor: canonical
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as restricted TLS certificate user
  2. Delivery
    Send PUT/PATCH request to /1.0/certificates/{fingerprint}
  3. Exploit
    Omit Type field validation in doCertificateUpdate
  4. Execution
    Escalate privileges to cluster admin
  5. Impact
    Gain 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.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

LXD 5.1.0 <5.21.5
LXD 6.0.0 <6.8.0
LXD 4.12.0 <5.0.7

Affected Packages

go github.com/canonical/lxd no fix
euvd lxd fix: 5.0.7, 5.21.5, 6.8.0

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

Vendor (canonical) PRIMARY 9.1 CRITICAL
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
SUSE CRITICAL

Primary rating from Vendor (canonical).

CVSS VectorVendor: canonical

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch released
Apr 09, 2026 - 09:30 nvd
Patch available
CVE Published
Apr 09, 2026 - 09:22 nvd
CRITICAL 9.1

DescriptionCVE.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

Why It Matters

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.

Business Impact: Severe
Compensating Controls

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

EPSS Score
0.1%
Top 75% exploitable
Threat Intel
1
1 source
Social Media
4
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA Vendor CIRCL GitHub

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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 3

More in Lxd

View all
CVE-2025-54286 HIGH POC
7.5 Oct 02

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

CVE-2025-54289 HIGH POC
7.4 Oct 02

Privilege escalation in Canonical LXD's operations API (LXD before 6.5 and LXD 5.21 before 5.21.4) allows an authenticat

CVE-2025-54293 HIGH POC
7.1 Oct 02

Authenticated remote attackers with access to the Canonical LXD instance log retrieval or deletion endpoints can read ar

CVE-2025-54287 HIGH POC
7.1 Oct 02

Server-side template injection in Canonical LXD's instance snapshot naming feature lets an authenticated user who can mo

CVE-2025-54290 MEDIUM POC
6.9 Oct 02

Unauthenticated project enumeration in Canonical LXD 5.21.x before 5.21.4 and 6.x before 6.5 lets remote attackers deter

CVE-2025-54291 MEDIUM POC
6.9 Oct 02

Unauthenticated remote attackers can confirm the existence of LXD projects on Canonical LXD by comparing HTTP status cod

CVE-2026-63294 CRITICAL
9.9 Aug 12

Privilege escalation to host root in Canonical LXD occurs when the container manager unpacks crafted image or backup arc

CVE-2026-66897 CRITICAL
9.9 Aug 24

Host root code execution in Canonical LXD arises from a path-traversal flaw in instance template processing, letting an

CVE-2026-63293 CRITICAL
9.9 Aug 12

Arbitrary host file read and write in Canonical LXD occurs because the image import/unpack routine does not verify wheth

CVE-2026-63298 CRITICAL
9.9 Aug 12

Canonical LXD's NVIDIA GPU passthrough configuration handler fails to sanitize newline characters in user-supplied `nvid

CVE-2026-66898 CRITICAL
9.9 Aug 12

Path traversal in Canonical's LXD container and VM manager allows a user with backup import/restore privileges to write

CVE-2026-62420 CRITICAL
9.9 Aug 12

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

Vendor StatusVendor

SUSE

Severity: Critical

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy