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.
CVE-2026-62940
This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% 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
- 49(Track)EG Risk 49/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%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
August 21, 2026
Last Modified
August 21, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026Project restriction bypass via instance migration config override · Advisory · lxc/incus · GitHub
https://github.com/lxc/incus/security/advisories/GHSA-qw5c-v953-38gwWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 17× 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 01:37 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 16:12 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 16:14 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 16:09 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 16:10 UTCEG score recompute
- 2026-08-24 12:08 UTCEG score recompute
- 2026-08-23 04:13 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 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-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p90CRITICAL
- CVE-2018-1217EG 9.8EPSS p97CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-62940?
When was CVE-2026-62940 disclosed?
Is CVE-2026-62940 actively exploited?
What is the CVSS score of CVE-2026-62940?
How do I remediate CVE-2026-62940?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62940
Is Your Infrastructure Affected by CVE-2026-62940?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.