Incus is a system container and virtual machine manager. Prior to version 7.3.0, when copying an instance across projects, the project restriction check (AllowInstanceCreation) runs BEFORE the source instance's configuration is merged into the request. Dangerous configuration keys (including security.privileged, raw.lxc, raw.apparmor) from the source instance are merged AFTER the check passes, bypassing all project restrictions on the target project. Version 7.3.0 patches the issue.
CVE-2026-62941
This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.9
- EG Score
- 9.9(medium)
- EG Risk
- 61(Track*)EG Risk 61/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity99% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
August 21, 2026
Last Modified
August 21, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026Project restriction bypass via cross-project instance copy · Advisory · lxc/incus · GitHub
https://github.com/lxc/incus/security/advisories/GHSA-mq9x-prm8-3vpwWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 02:09 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 01:07 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 15:15 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 18:27 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 17:06 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 16:10 UTCEG score recompute
- 2026-08-24 11:54 UTCEG score recompute
- 2026-08-23 02:35 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 17:21 UTCEG score recompute
- 2026-08-21 16:51 UTCEG score recompute
- 2026-08-21 15:21 UTCEG score recompute
- 2026-08-21 14:54 UTCEG score recompute
- 2026-08-21 14:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-62941?
When was CVE-2026-62941 disclosed?
Is CVE-2026-62941 actively exploited?
What is the CVSS score of CVE-2026-62941?
How do I remediate CVE-2026-62941?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62941
Is Your Infrastructure Affected by CVE-2026-62941?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.