ubuntu-cve-2026-62313
Vulnerability from osv_ubuntu
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": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "golang-github-lxc-incus-dev",
"binary_version": "6.0.0-1ubuntu0.3+esm3"
},
{
"binary_name": "incus",
"binary_version": "6.0.0-1ubuntu0.3+esm3"
},
{
"binary_name": "incus-agent",
"binary_version": "6.0.0-1ubuntu0.3+esm3"
},
{
"binary_name": "incus-client",
"binary_version": "6.0.0-1ubuntu0.3+esm3"
},
{
"binary_name": "incus-migrate",
"binary_version": "6.0.0-1ubuntu0.3+esm3"
},
{
"binary_name": "incus-tools",
"binary_version": "6.0.0-1ubuntu0.3+esm3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:24.04:LTS",
"name": "incus",
"purl": "pkg:deb/ubuntu/incus@6.0.0-1ubuntu0.3+esm3?arch=source\u0026distro=esm-apps/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"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"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "golang-github-lxc-incus-dev",
"binary_version": "6.0.5-8ubuntu0.26.04.1~esm1"
},
{
"binary_name": "incus",
"binary_version": "6.0.5-8ubuntu0.26.04.1~esm1"
},
{
"binary_name": "incus-agent",
"binary_version": "6.0.5-8ubuntu0.26.04.1~esm1"
},
{
"binary_name": "incus-base",
"binary_version": "6.0.5-8ubuntu0.26.04.1~esm1"
},
{
"binary_name": "incus-client",
"binary_version": "6.0.5-8ubuntu0.26.04.1~esm1"
},
{
"binary_name": "incus-extra",
"binary_version": "6.0.5-8ubuntu0.26.04.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:26.04:LTS",
"name": "incus",
"purl": "pkg:deb/ubuntu/incus@6.0.5-8ubuntu0.26.04.1~esm1?arch=source\u0026distro=esm-apps/resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.0.4-2",
"6.0.5-8",
"6.0.5-8ubuntu0.26.04.1~esm1"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2026-62313",
"modified": "2026-09-02T16:20:05Z",
"published": "2026-08-21T15:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-62313"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-62313"
},
{
"type": "REPORT",
"url": "https://github.com/lxc/incus/security/advisories/GHSA-53cg-qvg7-m8vg"
},
{
"type": "REPORT",
"url": "https://github.com/lxc/incus/pull/3750"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-62313"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.