CVE-2026-62313 Incus: Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated`
Attackers can bypass tenant isolation restrictions in Incus by omitting a specific configuration key, allowing shared host ID maps and weakening container isolation.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-62313?
CVE-2026-62313 is a medium-severity vulnerability in lxc incus, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Incus is a system container and virtual machine manager. Prior to version 7.3.0, project-level enforcement of `restricted.containers.privilege=isolated` can be trivially bypassed, allowing a user to create a non-isolated (shared host idmap) container in a project that is configured to forbid them. The restriction only rejects an explicitly set `security.idmap.isolated=false` (or empty) and fails to enforce anything when the key is omitted entirely. Because an unset `security.idmap.isolated` defaults to `false` (non-isolation), a user simply leaves the key out and obtains exactly the container state the restriction is meant to forbid. This defeats the tenant-isolation guarantee the restriction exists to provide. Containers in the project share the host uid/gid map instead of receiving unique, non-overlapping ranges, weakening the isolation boundary between co-tenant containers and the host. Version 7.3.0 patches the issue.
Weakness: CWE-863
Which versions are affected by CVE-2026-62313?
How do I fix CVE-2026-62313?
Upgrade to a fixed version.
Is CVE-2026-62313 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62313 exists.
Sources
Also known as DEBIAN-CVE-2026-62313, GHSA-53cg-qvg7-m8vg, UBUNTU-CVE-2026-62313.