CVE-2026-41684

Medium

Description

Incus is a system container and virtual machine manager. Prior to version 7.0.0, backup.GetInfo() trusts the inline backup/index.yaml config when present and only falls back to parsing the legacy backup/container/backup.yaml file if result.Config == nil. As a result, an archive can carry a valid inline config that passes the initial import preflight while also carrying a malformed legacy backup/container/backup.yaml file that is reparsed later from the restored file system. ParseConfigYamlFile() accepts YAML documents with no container section, and multiple downstream consumers then dereference. Container without checking for nil. Confirmed examples in the instance restore and import flow include backup.UpdateInstanceConfig() and internalImportFromBackup(). An authenticated user with permission to import instance backups may be able to crash the Incus daemon with a crafted backup archive whose inline backup/index.yaml is valid but whose extracted legacy backup.yaml omits container. The crash occurs in the restore path after archive extraction has begun. This issue has been patched in version 7.0.0.

SeverityMedium
CVSS6.5
Exploit probability—
ProductLinuxcontainers Incus
PublishedMay 7, 2026
First seenMay 7, 2026

How to fix

Update
  • linuxcontainers incus7.0.0 or later

Affected products

ProductAffected versionsFixed in
linuxcontainers incusv < 7.0.07.0.0
github.com/lxc/incus/v6/cmd/incusdGov ≤ 6.23.0—
github.com/lxc/incusGoNo range specified—
github.com/lxc/incus/v6GoNo range specified—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.