GO-2026-6319 CVE-2026-55622 GHSA-c9f5-j9c3-mhrg
Incus has a project restriction bypass in instance copy across projects in github.com/lxc/incus
High
Go
- Severity
- 7.7 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.34%
- Chance of exploitation in the next 30 days. Higher than 27.56% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-284 Improper Access Control
- Fix
- Available
- 2 packages have a fixed version
Description
Incus has a project restriction bypass in instance copy across projects in github.com/lxc/incus
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/lxc/incus | all versions |
No fix yet |
| github.com/lxc/incus/v6 | all versions |
No fix yet |
| github.com/lxc/incus/v7 | < 7.2.0 |
7.2.0 |
| github.com/lxc/incus/v7/cmd/incusd | < 7.2.0 |
7.2.0 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
github.com/lxc/incus/v7 Go → 7.2.0
- go
go get github.com/lxc/incus/v7@v7.2.0 && go mod tidy
github.com/lxc/incus/v7/cmd/incusd Go → 7.2.0
- go
go get github.com/lxc/incus/v7/cmd/incusd@v7.2.0 && go mod tidy
Severity breakdown
CVSS 3.1 7.7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-284: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How to prevent it
- Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-64f3-v33m-w89f Incus has a project restriction bypass for custom volume copy across projects | High | Also affects github.com/lxc/incus |
| GO-2026-5806 Incus has an arbitrary file write on its client due to trusted image hash | Critical | Also affects github.com/lxc/incus |
| GO-2026-5810 Incus: CreateCustomVolumeFromBackup nil-pointer dereference on volume_snapshots[*].expires_at (sibling-field variant of GHSA-r7w7) | Low | Also affects github.com/lxc/incus |
| GO-2026-5808 Incus has an argument injection in backup compression algorithm leading to AFW and ACE | Critical | Also affects github.com/lxc/incus |
| GO-2026-5800 Incus: Nil-pointer dereference in createDependentVolumesFromBackup on disk.{Volume,VolumeSnapshots,Pool} | Low | Also affects github.com/lxc/incus |
| GO-2026-5802 Incus has an arbitrary file write via path traversal in S3 multipart upload | Critical | Also affects github.com/lxc/incus |
| GO-2026-5803 Incus has arbitrary file read+write on host via templates/ symlink in malicious image | Critical | Also affects github.com/lxc/incus |
| GO-2026-5799 Incus has a restricted project bypass leading to arbitrary command execution | Critical | Also affects github.com/lxc/incus |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor