CVE-2026-55621

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity77% × 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

September 18, 2026

Advisory Details (1)

Auto-updated Aug 21, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Project restriction bypass for custom volume copy across projects · Advisory · lxc/incus · GitHub

https://github.com/lxc/incus/security/advisories/GHSA-64f3-v33m-w89f

Vendor 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

(7 across 4 ecosystems)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/lxc/incus———
github.com/lxc/incus/v6———
github.com/lxc/incus/v7—7.2.0—
Debian:13(2)
PackageVulnerable rangeFixed inDependents
incus6.0.4-2 ... 6.0.4-2+deb13u7~bpo12+1 (15 versions)6.0.4-2+deb13u8—
lxd5.0.2+git20231211.1364ae4-9 ... 5.0.2+git20231211.1364ae4-9+deb13u6 (7 versions)5.0.2+git20231211.1364ae4-9+deb13u7—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
lxd5.0.2+git20231211.1364ae4-1 ... 5.0.2-6 (17 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
incus6.0.4-2 ... 7.0.0-5~bpo13+1 (28 versions)7.0.0-5—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 49× 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.

  1. 2026-09-18 20:18 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 21:17 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 21:42 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 10:45 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 12:43 UTCEG score recompute
  10. 2026-09-15 03:11 UTCEPSS rescore
  11. 2026-09-13 16:50 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescore
  13. 2026-09-12 18:59 UTCEG score recompute
  14. 2026-09-11 21:07 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 10:11 UTCEG score recompute
  17. 2026-09-10 12:13 UTCEG score recompute
  18. 2026-09-10 09:35 UTCEPSS rescore
  19. 2026-09-09 01:47 UTCEG score recompute
  20. 2026-09-08 22:01 UTCEPSS rescore
  21. 2026-09-07 17:32 UTCEG score recompute
  22. 2026-09-07 16:01 UTCEPSS rescore
  23. 2026-09-06 19:41 UTCEG score recompute
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-05 21:44 UTCEG score recompute
Show 24 more
  1. 2026-09-04 23:49 UTCEG score recompute
  2. 2026-09-04 11:36 UTCEG score recompute
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-01 17:32 UTCEG score recompute
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 06:35 UTCEG score recompute
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-30 21:26 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 10:30 UTCEG score recompute
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 01:07 UTCEG score recompute
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 15:50 UTCEG score recompute
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 17:52 UTCEG score recompute
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-24 21:53 UTCEG score recompute
  19. 2026-08-24 10:57 UTCEG score recompute
  20. 2026-08-23 02:08 UTCEG score recompute
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 15:21 UTCEG score recompute
  23. 2026-08-21 14:54 UTCEG score recompute
  24. 2026-08-21 14:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55621?
CVE-2026-55621 is a high vulnerability published on August 21, 2026. 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…
When was CVE-2026-55621 disclosed?
CVE-2026-55621 was first published in the National Vulnerability Database on August 21, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55621 actively exploited?
CVE-2026-55621 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.7% of all scored CVEs.
What is the CVSS score of CVE-2026-55621?
CVE-2026-55621 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-55621?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55621, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55621

Explore →

Is Your Infrastructure Affected by CVE-2026-55621?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs