How severe is CVE-2026-34177?

CVE-2026-34177 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-34177 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-34177?

CVE-2026-34177 affects Canonical Lxd. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-34177?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-34177 have an EU (EUVD) identifier?

Yes. CVE-2026-34177 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-20872.

When was CVE-2026-34177 published?

CVE-2026-34177 was published on 2026-04-09 and last updated on 2026-06-17.

CVE-2026-34177

CVE-2026-34177 is a critical-severity vulnerability in Canonical Lxd with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-184.

Key facts

Severity: Critical (CVSS 3.x base score 9.1)
EPSS exploit prediction: 0% (28th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-20872
Weakness: CWE-184
Affected product: Canonical Lxd
Published: 2026-04-09
Last modified: 2026-06-17

Description

Canonical LXD versions 4.12 through 6.7 contain an incomplete denylist in isVMLowLevelOptionForbidden (lxd/project/limits/permissions.go), which omits raw.apparmor and raw.qemu.conf from the set of keys blocked under the restricted.virtual-machines.lowlevel=block project restriction. A remote attacker with can_edit permission on a VM instance in a restricted project can inject an AppArmor rule and a QEMU chardev configuration that bridges the LXD Unix socket into the guest VM, enabling privilege escalation to LXD cluster administrator and subsequently to host root.

Frequently asked questions

What is CVE-2026-34177?: Canonical LXD versions 4.12 through 6.7 contain an incomplete denylist in isVMLowLevelOptionForbidden (lxd/project/limits/permissions.go), which omits raw.apparmor and raw.qemu.conf from the set of keys blocked under the restricted.virtual-machines.lowlevel=block project restriction. A remote attacker with can_edit permission on a VM instance in a restricted project can inject an AppArmor rule and a QEMU chardev configuration that bridges the LXD Unix socket into the guest VM, enabling privilege escalation to LXD cluster administrator and subsequently to host root.
How severe is CVE-2026-34177?: CVE-2026-34177 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-34177 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-34177?: CVE-2026-34177 affects Canonical Lxd. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-34177?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-34177 have an EU (EUVD) identifier?: Yes. CVE-2026-34177 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-20872.
When was CVE-2026-34177 published?: CVE-2026-34177 was published on 2026-04-09 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:canonical:lxd:*:*:*:*:*:*:*:*

More vulnerabilities in Canonical Lxd

CVE-2026-34179 — Critical (CVSS 9.1): In Canonical LXD versions 4.12 through 6.7, the doCertificateUpdate function in lxd/certificates.go does not validate…
CVE-2026-34178 — Critical (CVSS 9.1): In Canonical LXD before 6.8, the backup import path validates project restrictions against backup/index.yaml in the…
CVE-2025-54286 — High (CVSS 8.8): Cross-Site Request Forgery (CSRF) in LXD-UI in Canonical LXD versions >= 5.0 on Linux allows an attacker to create and…
CVE-2026-12411 — High (CVSS 8.4): Broken Access Control in the devLXDInstancePatchHandler component of Canonical LXD allows an untrusted guest to mount,…
CVE-2025-54289 — High (CVSS 8.1): Privilege Escalation in operations API in Canonical LXD <6.5 on multiple platforms allows attacker with read…
CVE-2026-9640 — High (CVSS 7.2): A privilege escalation vulnerability exists in LXD from 6.0 before 6.9, 5.21.0 before 5.21.5, and 5.0.0 before 5.0.7…

All CVEs affecting Canonical Lxd →

Other CWE-184 vulnerabilities

CVE-2026-28363 — Critical (CVSS 9.9): In OpenClaw before 2026.2.23, tools.exec.safeBins validation for sort could be bypassed via GNU long-option…
CVE-2026-56315 — Critical (CVSS 9.8): picklescan before 1.0.4 fails to block at least seven Python standard library modules (including uuid, _osx_support,…
CVE-2026-53873 — Critical (CVSS 9.8): picklescan before 1.0.4 contains an incomplete blocklist for the profile module that fails to block the module-level…
CVE-2025-71323 — Critical (CVSS 9.8): picklescan before 0.0.33 fails to block the ctypes module, allowing attackers to achieve remote code execution by…
CVE-2025-71320 — Critical (CVSS 9.8): picklescan before 0.0.33 contains an incomplete deny-list that fails to block pydoc.locate and operator.methodcaller…
CVE-2026-41264 — Critical (CVSS 9.8): Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, the specific…

Browse all CWE-184 vulnerabilities →