{"id":"CVE-2026-62313","aliases":["DEBIAN-CVE-2026-62313","EUVD-2026-63986","GHSA-53cg-qvg7-m8vg","UBUNTU-CVE-2026-62313","openSUSE-SU-2026:11651-1"],"status":"published","title":"Incus: Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated`","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.","severity":{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.0036,"percentile":0.30185,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-863"],"published":"2026-08-21T14:44:27Z","modified":"2026-10-28T02:30:22Z","fixes":[{"ecosystem":"Debian:13","package":"incus","fixed_in":["6.0.4-2+deb13u9"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"incus","fixed_in":["7.0.1-2"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:13","package":"incus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.0.4-2+deb13u9"}]}],"versions":["6.0.4-2","6.0.4-2+deb13u1","6.0.4-2+deb13u1~bpo12+1","6.0.4-2+deb13u2","6.0.4-2+deb13u2~bpo12+1","6.0.4-2+deb13u3","6.0.4-2+deb13u3~bpo12+1","6.0.4-2+deb13u4","6.0.4-2+deb13u4~bpo12+1","6.0.4-2+deb13u5","6.0.4-2+deb13u5~bpo12+1","6.0.4-2+deb13u6","6.0.4-2+deb13u6~bpo12+1","6.0.4-2+deb13u7","6.0.4-2+deb13u7~bpo12+1","6.0.4-2+deb13u8"]},{"source":"osv","ecosystem":"Debian:14","package":"incus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.1-2"}]}],"versions":["6.0.4-2","6.0.4-3","6.0.5-1","6.0.5-2","6.0.5-3","6.0.5-4","6.0.5-5","6.0.5-6","6.0.5-7","6.0.5-8","6.0.6-1","6.0.6-2","6.0.6-3","6.14.0-1~exp1","6.15.0-1~exp1","6.16.0-1~exp1","6.17.0-1~exp1","6.20.0-1~exp1","6.21.0-1~exp1","6.22.0-1~exp1","6.23.0-1~exp1","7.0.0-1","7.0.0-1~bpo13+1","7.0.0-2","7.0.0-2~bpo13+1","7.0.0-3","7.0.0-4","7.0.0-5","7.0.0-5~bpo13+1","7.0.1-1","7.0.1-1~bpo13+1","7.0.1-2~bpo13+1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:24.04:LTS","package":"incus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.4-1ubuntu1","0.5.1-1","0.5.1-3","0.6-1","6.0.0-1","6.0.0-1ubuntu0.1","6.0.0-1ubuntu0.2","6.0.0-1ubuntu0.2+esm1","6.0.0-1ubuntu0.3","6.0.0-1ubuntu0.3+esm1","6.0.0-1ubuntu0.3+esm2","6.0.0-1ubuntu0.3+esm3"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"incus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.5-8","7.0.1-5"]},{"source":"osv","ecosystem":"Ubuntu:Pro:26.04:LTS","package":"incus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.4-2","6.0.5-8","6.0.5-8ubuntu0.26.04.1~esm1"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"incus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.4-1.1"}]}],"bundled":21}],"products":[{"vendor":"lxc","product":"incus"}],"references":[{"url":"https://github.com/lxc/incus/security/advisories/GHSA-53cg-qvg7-m8vg","tags":["x_refsource_CONFIRM","exploit","advisory","report"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/62xxx/CVE-2026-62313.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62313","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-62313","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-62313","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-62313","tags":["report"]},{"url":"https://github.com/lxc/incus/pull/3750","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2026-39402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-47753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48750","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48769","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55621","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-62313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-62867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-62940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-62941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81501","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2026-62313","title":"Incus: Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated`","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.","status":"published","published":"2026-08-21T14:44:27.324Z","modified":"2026-08-26T17:27:33.674Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","level":"medium","assessor":"cna"}],"cwes":["CWE-863"],"updated_at":"2026-11-02T14:20:14.999906Z"}],"euvd":[{"id":"EUVD-2026-63986","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.","status":"published","published":"2026-08-21T14:44:27Z","modified":"2026-08-26T17:27:33Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","level":"medium"}],"updated_at":"2026-11-02T18:01:30.542287Z"}],"nvd":[{"id":"CVE-2026-62313","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.","status":"published","published":"2026-08-21T15:16:45.867Z","modified":"2026-10-15T19:10:00.173Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","level":"medium","assessor":"secondary"}],"cwes":["CWE-863"],"updated_at":"2026-11-02T14:12:40.665005Z"}],"osv":[{"id":"CVE-2026-62313","title":"Incus: Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated`","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.","status":"published","published":"2026-08-21T14:44:27.324Z","modified":"2026-10-28T02:30:22.210969003Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","level":"medium"}],"cwes":["CWE-863"],"updated_at":"2026-11-02T15:45:13.306117Z"},{"id":"DEBIAN-CVE-2026-62313","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.","status":"published","published":"2026-08-21T15:16:45.867Z","modified":"2026-10-16T09:47:29.059233945Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","level":"medium"}],"updated_at":"2026-11-02T15:45:57.932517Z"},{"id":"UBUNTU-CVE-2026-62313","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.","status":"published","published":"2026-08-21T15:16:00Z","modified":"2026-10-17T13:00:30.928595238Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","level":"medium"}],"updated_at":"2026-11-02T16:56:43.630667Z"},{"id":"openSUSE-SU-2026:11651-1","title":"incus-7.4-1.1 on GA media","description":"These are all security issues fixed in the incus-7.4-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-08-31T00:00:00Z","modified":"2026-09-01T09:30:03.89107478Z","updated_at":"2026-11-02T16:58:39.516824Z"}]}}