CVE-2026-62313 lxc CVE debrief

Who should care

Defenders responsible for managing Incus configurations and ensuring tenant isolation should assess exposure and prioritize verification of Incus versions and configurations. Defenders must verify Incus configurations to ensure enforcement of restricted.containers.privilege=isolated. Tenant isolation may be weakened if project-level enforcement is bypassed. Containers in the project may share the host uid/gid map instead of receiving unique, non-overlaping

Why it matters

CVE-2026-62313 allows bypass of project-level enforcement of restricted.containers.privilege=isolated in Incus, weakening tenant isolation. Defenders should assess exposure and prioritize verification of Incus versions and configurations.

• Defenders must verify Incus configurations to ensure enforcement of restricted.containers.privilege=isolated.
• Tenant isolation may be weakened if project-level enforcement is bypassed.
• Containers in the project may share the host uid/gid map instead of receiving unique, non-overlapping ranges.

Technical 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. Incus

Defensive priority

Defenders should assess exposure and prioritize verification of Incus versions, focusing on configurations where project-level enforcement of restricted.containers.privilege=isolated is critical.

Recommended defensive actions

• Assess exposure by verifying Incus versions in use and configurations where project-level enforcement of restricted.containers.privilege=isolated is critical.
• Prioritize verification of Incus configurations to ensure enforcement of restricted.containers.privilege=isolated.
• Update Incus to version 7.3.0 or later to patch the issue.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in Incus, a system container and virtual machine manager, where project-level enforcement of restricted.containers.privilege=isolated can be bypassed.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.