Categories
CVE-2026-48754

Vulnerability in github.com/lxc/incus/v7/cmd/incusd (CVE-2026-48754)

Summary

Vulnerability in github.com/lxc/incus/v7/cmd/incusd (CVE-2026-48754). Risk of unauthorized operations or information disclosure. Exploitable via POST /1.0/instances. Mitigation: upgrade to 7.1.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.1.0, (*backend).createDependentVolumesFromBackup in internal/server/storage/backend.go contains a cluster of unguarded pointer derefs on every dependent-volume entry's VolumeSnapshots[i], Volume, and Pool sub-fields. An authenticated user with can_create_instances permission on any project can crash the incusd daemon by uploading an instance backup tarball whose dependent_volumes[*] block contains a nil snapshot pointer (or omits volume: / pool:). This is a sibling-field variant of the 2026-05-04 batch fix d768f81c0a1d985f35ae56219519822b080bf5e3 ("Properly check dependent volumes on import"). That commit added if disk == nil at the top of the outer loop, but did not guard the four sub-pointer fields the loop body dereferences naked. Version 7.1.0 contains an updated patch.

Source: GitHub Security Advisories (Global) 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-48754 has been found in github.com/lxc/incus/v7/cmd/incusd.
Attackers can target a specific entry point like POST /1.0/instances over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/lxc/incus/v7/cmd/incusd to 7.1.0 or later.
If unsure, ask your IT team or search "github.com/lxc/incus/v7/cmd/incusd CVE-2026-48754" on the vendor's site.

CVE-2026-48754 (github.com/lxc/incus/v7/cmd/incusd) — CWE-476
Attack surface: POST /1.0/instances / Volume / Pool / can_create_instances
Patched: 7.1.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-476) exists in github.com/lxc/incus/v7/cmd/incusd. Attackers reach the vulnerable code path via POST /1.0/instances.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/lxc/incus/v7/cmd/incusd. Attack surface: POST /1.0/instances / Volume / Pool / can_create_instances.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.1.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 POST /1.0/instances requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/lxc/incus/v7/cmd/incusd' . 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/cmd/incusd' . | grep -v node_modules

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

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /1.0/instances' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /1.0/instances への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade github.com/lxc/incus/v7/cmd/incusd to 7.1.0

    ステージング環境で 7.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against POST /1.0/instances on staging to confirm patch closes the vector

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

Affected packages

go github.com/lxc/incus/v7/cmd/incusd
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"7.1.0"}]}]
Go github.com/lxc/incus
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go github.com/lxc/incus/v6
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go github.com/lxc/incus/v7
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"7.1.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