Bug 2521023 (CVE-2026-62313) - CVE-2026-62313 github.com/lxc/incus: Incus: Project restriction bypass weakens container isolation
Summary: CVE-2026-62313 github.com/lxc/incus: Incus: Project restriction bypass weaken...
Keywords:
Status: NEW
Alias: CVE-2026-62313
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2521985
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-21 15:13 UTC by OSIDB Bzimport
Modified: 2026-08-24 15:00 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-21 15:13:22 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.