Incus: Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated`
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-62313
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 18:14 UTC · Revision 1
Source evidence
Incus: Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated`
core-osv · Original sourcePublished 21 Aug 2026, 14:44 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.
osv:CVE-2026-62313
Complete source record
{
"id": "92a593afab1d3ff958dd96e9a2dec207cb6161612d44de367852a0250788f7ba",
"url": "https://osv.dev/vulnerability/CVE-2026-62313",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Incus: Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated`",
"summary": "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.",
"evidence": "osv:CVE-2026-62313",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-62313",
"aliases": [
"CVE-2026-62313",
"GHSA-53cg-qvg7-m8vg"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/lxc/incus",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "90429bf42f08b41c091e799d81465ff24b5cee2b"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "7.3.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"introduced": "0"
},
{
"fixed": "7.3.0"
}
],
"source": "DESCRIPTION"
}
]
}
}
],
"versions": [
"v7.2.0",
"v7.0.0",
"v7.1.0",
"v6.23.0",
"v6.22.0",
"v6.21.0",
"v6.20.0",
"v6.19.1",
"v6.19.0",
"v6.18.0",
"v6.17.0",
"v6.16.0",
"v6.14.0",
"v6.15.0",
"v6.13.0",
"v6.12.0",
"v6.11.0",
"v6.10.1",
"v6.10.0",
"v6.9.0",
"v6.8.0",
"v6.7.0",
"v6.6.0",
"v6.5.0",
"v6.4.0",
"v6.3.0",
"v6.2.0",
"v6.0.0",
"v6.1.0",
"v0.7.0",
"v0.6.0",
"v0.5.1",
"v0.5.0",
"v0.4.0",
"v0.3.0",
"v0.2.0",
"v0.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-62313.json"
}
}
],
"modified": "2026-10-28T02:30:22.210969003Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/62xxx/CVE-2026-62313.json",
"https://github.com/lxc/incus/security/advisories/GHSA-53cg-qvg7-m8vg",
"https://nvd.nist.gov/vuln/detail/CVE-2026-62313"
],
"provider_metadata": {
"cwe_ids": [
"CWE-863"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/62xxx/CVE-2026-62313.json"
}
},
"related_cves": [
{
"value": "CVE-2026-62313",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 488227,
"published_at": "2026-08-21T14:44:27.324+00:00"
}