CVE-2026-62940: Incus has a project restriction bypass via instance migration config override
Incus is a system container and virtual machine manager. Prior to version 7.3.0, when migrating an instance to another cluster member, user-supplied configuration overrides (including security-critical keys like `security.privileged` and `raw.lxc`) are applied without any project restriction enforcement, allowing a restricted project user to escalate to a privileged container and escape to the host. Version 7.3.0 patches the issue.
Security readout for executives and security teams
Plain-English summary
A restricted Incus project user can abuse instance migration settings to create a privileged container, potentially escaping to the host. This crosses a tenant security boundary and could expose host systems and other workloads. Incus versions before 7.3.0 are affected.
Executive priority
Treat as an immediate remediation priority for affected clustered environments. Successful abuse could compromise the host and workloads beyond the attacker's restricted project. Rapidly identify exposed deployments, limit migration privileges, and upgrade to 7.3.0 or later.
Technical view
During migration to another cluster member, Incus applies user-supplied configuration overrides without enforcing project restrictions. Security-sensitive keys such as security.privileged and raw.lxc can therefore enable privilege escalation and host escape. This is an authorization failure classified as CWE-862 and fixed in version 7.3.0.
Likely exposure
Exposure is highest for clustered Incus deployments below 7.3.0 where restricted project users can migrate instances and supply configuration overrides. Systems without affected versions or this user access path are not identified as vulnerable by the supplied evidence.
Exploitation context
The flaw is network-reachable, low-complexity, requires low privileges, and needs no user interaction according to CVSS 3.1. The supplied sources do not report active exploitation, and the CVE is not listed as KEV in the bundle.
Researcher notes
The vulnerable boundary is migration-time configuration validation, not ordinary project restriction definition. Assessment should focus on whether attacker-controlled overrides reach destination instance configuration without restriction enforcement. The bundle establishes host-escape impact but provides no evidence of exploitation in the wild.
Mitigation direction
Upgrade Incus to version 7.3.0 or later.
Until upgraded, restrict untrusted users from migrating instances between cluster members.
Review vendor guidance for any additional supported mitigations or operational precautions.
Prioritize hosts supporting sensitive workloads or multiple restricted projects.
Validation and detection
Inventory Incus versions and identify every deployment below 7.3.0.
Identify clustered deployments where restricted project users can initiate instance migrations.
Review migrated instance configurations for unexpected privileged or raw LXC settings.
Confirm project restrictions remain effective during authorized migration testing after upgrading.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.