Get real-time updates on Telegram
CVE-2026-34179: lxd from 4.12 (inclusive), through 5.0.6 (inclusive), from 5.21.0 (inclusive), through 5.21.4 (inclusive), from 6.0…
CVE-2026-34179 affects incus. CVSS 3.1 base score 9.1 (CRITICAL, Vendor/CNA). EPSS 0.00274 (percentile 0.19557), scored 26-Oct-2026. Fixed version: 6.0.4-2+deb13u6. Fixed version: 6.0.6-3. Fixed version: 5.0.2+git20231211.1364ae4-9+deb13u5.
Affected technology
lxd · from 4.12 (inclusive), through 5.0.6 (inclusive)
canonical
lxd · from 5.21.0 (inclusive), through 5.21.4 (inclusive)
canonical
lxd · from 6.0 (inclusive), through 6.7 (inclusive)
canonical
lxd · 4.12.0 to before 5.0.7, 5.1.0 to before 5.21.5, 6.0.0 to before 6.8.0
Canonical
Description’s affected range: versions 4.12 through 6.7
Component: Not specified by the source
File: permissions.go
Attack conditions (Vendor/CNA, CVSS 3.1): Network (remote) · High privileges required · No user interaction required
What an attacker can do
The source says 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. Vendor/CNA’s CVSS 3.1 assessment (base score 9.1/10) rates confidentiality, integrity and availability impact as high.
- CWE
- CWE-915
- Product
- incus
- CCR priority
- 36.5 /100 (P4)
- CVSS 3.1
- 9.1 /10 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H · Vendor/CNA
- EPSS
- 0.00278 · percentile 0.20463 · 2026-11-15
- KEV
- no
Provenance
- FIRST EPSS daily exploit-probability · Source record · observed 2026-11-16 06:41:02.068004+00:00 UTC
- NVD CVE API 2.0 · Source record · observed 2026-10-27 00:51:15.792435+00:00 UTC
- OSV.dev · Source record · observed 2026-10-27 11:47:01.753480+00:00 UTC
Stable permalink: https://cybercodered.org/item/cve-cve-2026-34179.html