CVSS 3.1
7.7 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NHigh (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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:Ngithub.com/lxc/incus/v7 (Go): fixed in 7.2.0Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| 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 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-64f3-v33m-w89f | Go | github.com/lxc/incus/v7 | <7.2.0 | 7.2.0 |
| GHSA-64f3-v33m-w89f | Go | github.com/lxc/incus/v6 | <=6.23.0 | no fix published |
| GHSA-64f3-v33m-w89f | Go | github.com/lxc/incus | <=0.7.0 | no fix published |
| GO-2026-6318 | Go | github.com/lxc/incus | all versions | no fix published |
| GO-2026-6318 | Go | github.com/lxc/incus/v6 | all versions | no fix published |
| GO-2026-6318 | Go | github.com/lxc/incus/v7 | <7.2.0 | 7.2.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | lxd | no fix listed | DEBIAN-CVE-2026-55621 |
| Debian | 13 | incus | 6.0.4-2+deb13u8 | DEBIAN-CVE-2026-55621 |
| Debian | 13 | lxd | 5.0.2+git20231211.1364ae4-9+deb13u7 | DEBIAN-CVE-2026-55621 |
| Debian | 14 | incus | 7.0.0-5 | DEBIAN-CVE-2026-55621 |
| Ubuntu | 20.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS | lxd | no fix listed | UBUNTU-CVE-2026-55621 |
| Ubuntu | 25.10, 26.10, Pro:24.04:LTS and 1 more | incus | no fix listed | UBUNTU-CVE-2026-55621 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | govulncheck-vulndb | 0.0.20260902T191204-160000.1.1 | SUSE-SU-2026:23692-1 SUSE-SU-2026:23712-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260902T191204-160000.1.1 | openSUSE-SU-2026:21812-1 |
| openSUSE | Tumbleweed | incus | 7.4-1.1 | openSUSE-SU-2026:11651-1 |
| Alpine | v3.24 | incus | 7.0.1-r0 | ALPINE-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.
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).