Skip to content
Fencer Intel
high 7.7

CVE-2026-55621 json

Incus has a project restriction bypass for custom volume copy across projects

published 2mo ago modified 5d ago also EUVD-2026-63984 , GHSA-64f3-v33m-w89f , GO-2026-6318

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/lxc/incus/v7 7.2.0
  • linuxcontainers incus 7.2.0
  • lxd Debian 13 5.0.2+git20231211.1364ae4-9+deb13u7
  • incus Debian 13 6.0.4-2+deb13u8
  • incus Debian 14 7.0.0-5

debian advisories DEBIAN-CVE-2026-55621

  • govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260902T191204-160000.1.1

suse advisories SUSE-SU-2026:23692-1SUSE-SU-2026:23712-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260902T191204-160000.1.1
  • incus openSUSE Tumbleweed 7.4-1.1

opensuse advisories openSUSE-SU-2026:21812-1openSUSE-SU-2026:11651-1

  • incus Alpine 3.24 7.0.1-r0

alpine advisories ALPINE-CVE-2026-55621

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-55621 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2mo ago

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/lxc/incus/v7
<7.2.0
7.2.0
go github.com/lxc/incus/v6
<=6.23.0
all versions
 no fix listed
go github.com/lxc/incus
<=0.7.0
all versions
 no fix listed

Affected products

  • lxc incus
  • canonical lxd

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.