dbcve.org
LxdApplication · Canonical

CVE-2026-34179

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to after 6.7 or later.
See remediation →
97/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LxdApplication
Affected:>= 4.12, <= 5.0.6>= 5.21.0, <= 5.21.4>= 6.0, <= 6.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 6.7
Vendor patch github.com →
Recommended fix High confidence

LXD 6.8 or later (any version greater than 6.7)

  1. 1. Identify your current LXD version using: lxd --version
  2. 2. Stop all LXD instances and services before upgrading to prevent data corruption
  3. 3. For Ubuntu-based systems, update the package index: sudo apt update
  4. 4. Upgrade LXD to the latest available version: sudo snap refresh lxd or sudo apt upgrade lxd
  5. 5. Verify the new version is installed: lxd --version
  6. 6. Ensure LXD service starts correctly: sudo systemctl start lxd
  7. 7. Test that the /1.0/certificates endpoint now properly validates the Type field for restricted users
  8. 8. Review that restricted TLS certificate users can no longer escalate privileges to cluster admin
Caveat Upgrade to a new major LXD version may require careful planning; review LXD release notes for any breaking changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34179 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34179 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data