Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.7amended

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

CVE-2026-55621GHSA-64f3-v33m-w89f

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/lxc/incus/v6

    Affected
    <= 6.23.0
    Fixed in
    no fixed version recorded

  • Go github.com/lxc/incus/v7

    Affected
    < 7.2.0
    Fixed in
    7.2.0

  • Go github.com/lxc/incus

    Affected
    <= 0.7.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2026-55621: 0.34% estimated exploitation activity in the next 30 days; percentile 27.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-64f3-v33m-w89f

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6318

  3. Revision 1 · created ·

    Published from osv record GHSA-64f3-v33m-w89f

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55621

Advisory: Incus has a project restriction bypass for custom volume copy across projects
IDs: CVE-2026-55621, GHSA-64f3-v33m-w89f
Record: https://patchnext.com/advisories/cve-2026-55621 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/lxc/incus/v7 7.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/lxc/incus/v6: affected <= 6.23.0
- Go github.com/lxc/incus/v7: affected < 7.2.0; fixed in 7.2.0
- Go github.com/lxc/incus: affected <= 0.7.0

## Suggested inspection (read-only)
- Go github.com/lxc/incus/v6: check the installed version with your package manager.
- Go github.com/lxc/incus/v7: check the installed version with your package manager.
- Go github.com/lxc/incus: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/lxc/incus/v6, github.com/lxc/incus/v7, github.com/lxc/incus.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-64f3-v33m-w89f (OSV record GHSA-64f3-v33m-w89f lists affected ranges: Go github.com/lxc/incus/v7 >=0 =0 =0 <=0.7.0)
- Verified: https://osv.dev/vulnerability/GO-2026-6318 (OSV record GO-2026-6318 lists affected ranges: Go github.com/lxc/incus >=0; Go github.com/lxc/incus/v6 >=0; Go github.com/lxc/incus/v7 >=0 <7.2.0 (fixed))
- Verified: https://github.com/advisories/GHSA-64f3-v33m-w89f (GitHub-reviewed advisory GHSA-64f3-v33m-w89f lists affected ranges: Go github.com/lxc/incus/v7 >=0 =0 =0 <=0.7.0)

Commands are suggestions: review each one before running it.

Loading voting…