CVE-2026-62313
Published:August 21, 2026
Updated:September 24, 2026
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.
Affected Packages
github.com/lxc/incus/v7 (GO):
Affected version(s) >=v7.0.0-20260813232705-b5505a7b3004 <v7.3.0Fix Suggestion:
Update to version v7.3.0Related Resources (3)
Do you need more information?
Contact UsCVSS v4
Base Score:
5.3
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
LOW
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
NONE
Vulnerable System Availability
LOW
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
4.3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Weakness Type (CWE)
Incorrect Authorization
EPSS
Base Score:
0.26