Security readout for executives and security teams
Plain-English summary
Incus before 7.3.0 can let a permitted user carry restricted, high-risk settings into another project by copying an instance. Because validation happens before the source configuration is added, the target project’s safeguards can be bypassed, potentially compromising confidentiality, integrity, and availability beyond that project.
Executive priority
Treat as an immediate remediation priority for multi-project or multi-tenant Incus environments. A low-privileged user may bypass a core isolation control and introduce privileged configuration across project boundaries. Upgrade promptly and temporarily restrict cross-project copying where rapid patching is not possible.
Technical view
This is a TOCTOU authorization flaw in cross-project instance copying. AllowInstanceCreation checks target-project restrictions before merging the source instance configuration. The later merge can introduce prohibited keys such as security.privileged, raw.lxc, and raw.apparmor without another restriction check. The issue is classified as CWE-863 and fixed in Incus 7.3.0.
Likely exposure
Deployments running Incus earlier than 7.3.0 are affected where users can copy instances across projects. Risk is greatest when target-project restrictions are relied upon to isolate lower-privileged or untrusted users. The supplied sources do not identify affected configurations beyond this workflow.
Exploitation context
The CVSS 3.1 score is 9.9, with network reachability, low complexity, low privileges, no user interaction, and changed scope. The supplied bundle does not provide evidence of active exploitation, and the CVE is not identified as KEV.
Researcher notes
The authorization decision is made against an incomplete request state, creating a check-use gap during configuration merging. Assessment should focus on cross-project copy authorization, inherited instance keys, and whether sensitive target-project restrictions were expected to block those keys. The supplied evidence does not establish public exploit availability or observed attacks.
Mitigation direction
- Upgrade Incus to version 7.3.0 or later.
- Until upgraded, prevent untrusted users from copying instances across projects.
- Review the vendor advisory for deployment-specific guidance.
- Prioritize environments relying on project restrictions for tenant or privilege separation.
Validation and detection
- Inventory Incus deployments and confirm their exact running versions.
- Identify users and integrations permitted to copy instances across projects.
- Review cross-project copies for prohibited configuration inherited from source instances.
- Confirm target-project restrictions are enforced after upgrading to 7.3.0 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-863: 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.
Open ATT&CK lookupContainer behavior lookup
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.
Open ATT&CK lookupCVE-2026-62941 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/lxc/incus/security/advisories/GHSA-mq9x-prm8-3vpwCVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.