Categories
CVE-2026-55621 high CVSS 7.7

Vulnerability in github.com/lxc/incus/v7 (CVE-2026-55621)

Summary

Vulnerability in github.com/lxc/incus/v7 (CVE-2026-55621). Confidential information can be exposed externally. Exploitable via req.Source.Project. Mitigation: upgrade to 7.2.0 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55621 has been found in github.com/lxc/incus/v7.
Attackers can target a specific entry point like req.Source.Project over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade github.com/lxc/incus/v7 to 7.2.0 or later.
If unsure, ask your IT team or search "github.com/lxc/incus/v7 CVE-2026-55621" on the vendor's site.

CVE-2026-55621 (github.com/lxc/incus/v7) — CWE-284 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: req.Source.Project / CreateCustomVolumeFromCopy / allowPermission / CanView
Patched: 7.2.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-284) exists in github.com/lxc/incus/v7. Attackers reach the vulnerable code path via req.Source.Project.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/lxc/incus/v7. Attack surface: req.Source.Project / CreateCustomVolumeFromCopy / allowPermission / CanView.

🔥 Severity

Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 7.2.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/lxc/incus/v7' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/lxc/incus/v7' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/lxc/incus/v7 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/lxc/incus/v7 to 7.2.0

    ステージング環境で 7.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/lxc/incus/v7
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"7.2.0"}]}]
go github.com/lxc/incus/v6
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"6.23.0"}]}]
go github.com/lxc/incus
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"0.7.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details