Vulnerability in github.com/lxc/incus/v7/cmd/incusd (CVE-2026-48756)
Summary
Vulnerability in github.com/lxc/incus/v7/cmd/incusd (CVE-2026-48756). Risk of unauthorized operations or information disclosure. Exploitable via POST /1.0/storage-pools/. 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).CreateCustomVolumeFromBackup in internal/server/storage/backend.go contains an unguarded *time.Time dereference on the ExpiresAt field of every volume-snapshot entry in an imported custom-volume backup. An authenticated user with can_create_storage_volumes permission on any project can crash the incusd daemon by uploading a backup tarball whose volume_snapshots[*].expires_at field is absent. This is a sibling-field variant of GHSA-r7w7-mmxr-47r9 (CVE-2026-40197). Commit 985a1dedf9f3e7ba729c93b654905ed510de25c2 added if s == nil at the top of the loop body, but did not guard the adjacent *snapshot.ExpiresAt deref 19 lines later. Every other consumer of Config.VolumeSnapshots[i].ExpiresAt in this same file already gates the deref with a nil-check — the asymmetric guard is the bug. 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-48756 has been found in github.com/lxc/incus/v7/cmd/incusd.
Attackers can target a specific entry point like POST /1.0/storage-pools/ 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-48756" on the vendor's site.
CVE-2026-48756 (github.com/lxc/incus/v7/cmd/incusd) — CWE-476
Attack surface: POST /1.0/storage-pools/ / ExpiresAt / can_create_storage_volumes / incusd
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.
A vulnerability (CWE-476) exists in github.com/lxc/incus/v7/cmd/incusd. Attackers reach the vulnerable code path via POST /1.0/storage-pools/.
Check the vendor advisory for the affected versions of github.com/lxc/incus/v7/cmd/incusd. Attack surface: POST /1.0/storage-pools/ / ExpiresAt / can_create_storage_volumes / incusd.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 7.1.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /1.0/storage-pools/ 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
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /1.0/storage-pools/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /1.0/storage-pools/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/lxc/incus/v7/cmd/incusd to 7.1.0ステージング環境で 7.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /1.0/storage-pools/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-48756 incus Fixed in: 6.0.4-2+deb13u8
- Ubuntu UBUNTU-CVE-2026-48756 lxd
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com