NVD / CVE Program· CNA canonical

CVE-2026-34177: VM lowlevel restriction bypass via raw.apparmor and raw.qemu.conf

CriticalCVSS 9.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 36/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Canonical lxd 5.0.7, 5.21.5, 6.8.0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Canonical lxd 5.0.7, 5.21.5, 6.8.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published: Apr 9, 2026
Updated: Oct 26, 2026
EPSS: 0.3% · 31th percentile
CWE: CWE-184

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 36 / 40 · 9.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · canonical: 9.1; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
canonical	lxd	cpe:2.3:a:canonical:lxd

Versions reported by the vendor

Affected version ranges reported by the assigning authority (canonical). Independent of NVD's CPE analysis and usually ahead of it.

Canonical lxd
- 4.12.0 and later · before 5.0.7affected · semver
- 5.1.0 and later · before 5.21.5affected · semver
- 6.0.0 and later · before 6.8.0affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

canonical lxd4.12 and later · up to 5.0.6 inclusive
canonical lxd5.21.0 and later · up to 5.21.4 inclusive
canonical lxd6.0 and later · up to 6.7 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	lxd	from 0	—
Debian:13	incus	before 6.0.2-1	6.0.2-1
Debian:13	lxd	before 5.0.2+git20231211.1364ae4-9+deb13u5	5.0.2+git20231211.1364ae4-9+deb13u5
Go	github.com/canonical/lxd	from 0.0.0-20210305023314-538ac3df036e	—
Go	github.com/canonical/lxd	from 0.0.0-20210305023314-538ac3df036e · up to and including 0.0.0-20260226085519-736f34afb267	—
openSUSE:Leap 16.0	govulncheck-vulndb	before 0.0.20260827T195228-160000.1.1	0.0.20260827T195228-160000.1.1
SUSE:Linux Enterprise Server 16.0	govulncheck-vulndb	before 0.0.20260827T195228-160000.1.1	0.0.20260827T195228-160000.1.1

Same product

canonical: all records

Other highest-scoring records for the same primary product.

CVE-2026-112816Improper certificate validation in the HTTPS listener in LXD
40Plan
CVE-2026-87799Arbitrary file write on LXD host via symlink in migration stream
39Monitor
CVE-2026-85526Path traversal via Btrfs optimized-backup subvolumes[].path enables root file/dir manipulation in LXD
39Monitor

Published before and after this one in the same product

← EarlierCVE-2026-3351Mar 3, 2026 · Authorization Bypass in LXD GET /1.0/certificates Endpoint
8Monitor
← EarlierCVE-2026-28384Mar 12, 2026 · Authenticated RCE via unsanitized compression_algorithm
37Monitor
Later →CVE-2026-34178Apr 9, 2026 · Importing a crafted backup leads to project restriction bypass
36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Canonical lxd	5.0.7	Vendor (CNA)
Canonical lxd	5.21.5	Vendor (CNA)
Canonical lxd	6.8.0	Vendor (CNA)
debian:incus	6.0.2-1 · Debian:13	Package registry (OSV)
debian:lxd	5.0.2+git20231211.1364ae4-9+deb13u5 · Debian:13	Package registry (OSV)
opensuse:govulncheck-vulndb	0.0.20260827T195228-160000.1.1 · openSUSE:Leap 16.0	Package registry (OSV)
suse:govulncheck-vulndb	0.0.20260827T195228-160000.1.1 · SUSE:Linux Enterprise Server 16.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.