CVE-2026-62313
Received Received - Intake

Privilege Escalation in Incus Container Manager

Publication date: 2026-08-21

Last updated on: 2026-08-21

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-21
Last Modified
2026-08-21
Generated
2026-08-21
AI Q&A
2026-08-21
EPSS Evaluated
N/A
NVD
CVE-2026-62313
EUVD
EUVD-2026-63986

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
canonical incus to 7.3.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-62313 is a vulnerability in Incus where project-level isolation restrictions can be bypassed. The system is designed to enforce container isolation by preventing non-isolated containers in restricted projects, but it only checks for explicit settings of `security.idmap.isolated=false` or empty values. When the key is omitted, the system fails to enforce restrictions, defaulting to non-isolation. This allows users to create non-isolated containers in projects meant to forbid them, defeating the intended tenant-isolation guarantee.

Detection Guidance

To detect this vulnerability, check if any Incus projects have containers with unset or explicitly set security.idmap.isolated=false. Run: incus project list to list projects, then for each project run: incus config trust list --project <project_name> to inspect container configurations. Look for containers where security.idmap.isolated is missing or set to false.

Impact Analysis

This vulnerability allows users to bypass isolation restrictions, creating non-isolated containers that share the host's UID/GID map. This can lead to denial of service by exhausting shared resources, loss of data integrity, and confidentiality breaches. Processes in one container may access or modify files owned by another tenant's UIDs if they share storage or mounts.

Compliance Impact

This vulnerability weakens tenant isolation by allowing containers to share the host's UID/GID map instead of using unique ranges. This could lead to unauthorized access between tenants, potentially violating confidentiality and integrity requirements in GDPR and HIPAA. Non-isolated containers may also allow resource exhaustion attacks, impacting availability.

Mitigation Strategies

Upgrade Incus to version 7.3.0 or later immediately. After upgrading, verify that project-level restrictions are enforced by testing container creation in restricted projects. Ensure all existing containers have security.idmap.isolated explicitly set to true where required.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-62313. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart