cve.bz

CVE-2026-55621 Improper Access Control

7.7 highEPSS 0.4%Fix available

High (7.7). EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/lxc/incus/v7 7.2.0.

On this page
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.

Severity

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-55621 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-55621?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-55621?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-55621 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
lxc incus< 7.2.0
canonical lxd>= 4.12.0, < 5.0.7
canonical lxd>= 5.1.0, 5.21.5
canonical lxd>= 6.0.0, < 6.8.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-64f3-v33m-w89fGogithub.com/lxc/incus/v7<7.2.07.2.0
GHSA-64f3-v33m-w89fGogithub.com/lxc/incus/v6<=6.23.0no fix published
GHSA-64f3-v33m-w89fGogithub.com/lxc/incus<=0.7.0no fix published
GO-2026-6318Gogithub.com/lxc/incusall versionsno fix published
GO-2026-6318Gogithub.com/lxc/incus/v6all versionsno fix published
GO-2026-6318Gogithub.com/lxc/incus/v7<7.2.07.2.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12lxdno fix listedDEBIAN-CVE-2026-55621
Debian13incus6.0.4-2+deb13u8DEBIAN-CVE-2026-55621
Debian13lxd5.0.2+git20231211.1364ae4-9+deb13u7DEBIAN-CVE-2026-55621
Debian14incus7.0.0-5DEBIAN-CVE-2026-55621
Ubuntu20.04:LTS, Pro:16.04:LTS, Pro:18.04:LTSlxdno fix listedUBUNTU-CVE-2026-55621
Ubuntu25.10, 26.10, Pro:24.04:LTS and 1 moreincusno fix listedUBUNTU-CVE-2026-55621
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20260902T191204-160000.1.1SUSE-SU-2026:23692-1 SUSE-SU-2026:23712-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260902T191204-160000.1.1openSUSE-SU-2026:21812-1
openSUSETumbleweedincus7.4-1.1openSUSE-SU-2026:11651-1
Alpinev3.24incus7.0.1-r0ALPINE-CVE-2026-55621

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON