Incus is a system container and virtual machine manager. Prior to version 7.2.0, missing authorization checks exist for custom volume copying where an attacker knowing the name of a project that they don't have access to and the name of a custom volume in that project can copy the custom volume to a new project. This issue could allow an attacker to access secrets in custom volumes they are not authorized to access. Version 7.2.0 patches the issue.
CVE-2026-55621
This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% 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
- 7.7
- EG Score
- 7.7(medium)
- EG Risk
- 39(Track)EG Risk 39/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 computedSeverity77% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
August 21, 2026
Last Modified
August 21, 2026
Advisory Details (1)
Auto-updated Aug 21, 2026Project restriction bypass for custom volume copy across projects · Advisory · lxc/incus · GitHub
https://github.com/lxc/incus/security/advisories/GHSA-64f3-v33m-w89fVendor Advisories for CVE-2026-55621(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 1 ecosystem)
Go(3)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/lxc/incus | — | — | — |
| github.com/lxc/incus/v6 | — | — | — |
| github.com/lxc/incus/v7 | — | 7.2.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 14× 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:22 UTCEPSS rescore
- 2026-08-29 01:07 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 15:50 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:52 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-24 21:53 UTCEG score recompute
- 2026-08-24 10:57 UTCEG score recompute
- 2026-08-23 02:08 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-284
Frequently asked(5)
What is CVE-2026-55621?
When was CVE-2026-55621 disclosed?
Is CVE-2026-55621 actively exploited?
What is the CVSS score of CVE-2026-55621?
How do I remediate CVE-2026-55621?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55621
Is Your Infrastructure Affected by CVE-2026-55621?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.