CVE-2026-34177
LXD 4.12–6.7: Privilege escalation via restricted-project bypass.
Is CVE-2026-34177 being exploited?
Not confirmed. CVE-2026-34177 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-34177?
CVE-2026-34177 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-34177?
Yes. A fix has been recorded for CVE-2026-34177. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-34177 affect?
CVE-2026-34177 affects Canonical LXD 4.12–6.7. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-34177?
Upgrade to fixed LXD version when available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker with can_edit on a restricted VM can inject AppArmor/QEMU config to bridge LXD socket, escalating to host root.
Immediate action required
- affected>= 4.12.0 and < 5.0.7
- affected>= 5.1.0 and < 5.21.5
- affected>= 6.0.0 and < 6.8.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.