CVSS 3.1
9.9 criticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCritical (9.9). EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/lxc/incus/v7/cmd/incusd 7.2.0.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:Hgithub.com/lxc/incus/v7/cmd/incusd (Go): fixed in 7.2.0github.com/lxc/incus/v7 (Go): fixed in 7.2.0Explain CVE-2026-48769 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48769?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48769?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-48769 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.0.0, < 4.0.11 |
| canonical lxd | >= 5.0.0, < 5.0.7 |
| canonical lxd | >= 5.1.0, < 5.21.5 |
| canonical lxd | >= 6.0.0, < 6.9.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-f6m5-xw2g-xc4x | Go | github.com/lxc/incus/v7/cmd/incusd | <7.2.0 | 7.2.0 |
| GO-2026-5806 | Go | github.com/lxc/incus | all versions | no fix published |
| GO-2026-5806 | Go | github.com/lxc/incus/v6 | all versions | no fix published |
| GO-2026-5806 | 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-48769 |
| Debian | 13 | incus | 6.0.4-2+deb13u8 | DEBIAN-CVE-2026-48769 |
| Debian | 13 | lxd | 5.0.2+git20231211.1364ae4-9+deb13u7 | DEBIAN-CVE-2026-48769 |
| Debian | 14 | incus | 7.0.0-5 | DEBIAN-CVE-2026-48769 |
| Ubuntu | 20.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS | lxd | no fix listed | UBUNTU-CVE-2026-48769 |
| Ubuntu | 25.10, 26.10, Pro:24.04:LTS and 1 more | incus | no fix listed | UBUNTU-CVE-2026-48769 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
| openSUSE | Tumbleweed | incus | 7.4-1.1 | openSUSE-SU-2026:11651-1 |
| Alpine | v3.24 | incus | 7.0.1-r0 | ALPINE-CVE-2026-48769 |
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 · openSUSE · Alpine.
Red Hat rates this Critical.
Incus is not shipped in any Red Hat product. The community Fedora package is affected.
No mitigation is needed as Incus is not shipped in any Red Hat product.
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-48769.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).