# CVE-2026-47753: Incus has a Nil-Pointer Dereference Panic via Instance Backup Import (volume omitted)

> An authenticated user can crash the Incus daemon by uploading a crafted backup tarball, causing denial of service across all projects.

- **Severity:** Medium 4.4 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-47753, GHSA-8g7m-96c8-8wwc, GO-2026-5252, UBUNTU-CVE-2026-47753

## What is CVE-2026-47753?

CVE-2026-47753 is a medium-severity vulnerability in lxc incus, published on 21 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incus is a system container and virtual machine manager. Prior to version 7.1.0, `(*backend).CreateInstanceFromBackup` in `internal/server/storage/backend.go` contains a nil-pointer dereference that an authenticated user with permission to create instances in any project can trigger remotely by uploading a crafted backup tarball. The Incus daemon panics and the process crashes, causing denial of service to every project on that cluster member. This is a sibling of `GHSA-fwj8-62r8-8p8m`, `GHSA-r7w7-mmxr-47r9`, and `GHSA-x5r6-jr56-89pv` (all assigned 2026-05-04). Those patches added guards on adjacent fields of the same `backup/config.Config` struct; the `Volume` field on the instance-import path was missed. Version 7.1.0 contains an updated patch.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-47753?

5 open source packages ship an affected version, including github.com/lxc/incus/v7, github.com/lxc/incus and github.com/lxc/incus/v6.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/lxc/incus/v7` | Go | All versions | 7.1.0 |
| `github.com/lxc/incus/v7` | Go | All versions | 7.1.0 |
| `github.com/lxc/incus/v7` | Go | All versions | 7.1.0 |
| `github.com/lxc/incus` | Go | All versions | None |
| `github.com/lxc/incus/v6` | Go | All versions | None |

## How do I fix CVE-2026-47753?

Upgrade github.com/lxc/incus/v7 to 7.1.0 or later.

## Is CVE-2026-47753 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47753 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47753 and fix it if it is affected.

What it is: CVE-2026-47753 is a medium-severity vulnerability in lxc incus, published on 21 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47753 exists.

Affected packages and fixed versions:
- github.com/lxc/incus/v7 (Go): affected all versions; fixed in 7.1.0
- github.com/lxc/incus/v7 (Go): affected all versions; fixed in 7.1.0
- github.com/lxc/incus/v7 (Go): affected all versions; fixed in 7.1.0
- github.com/lxc/incus (Go): affected all versions; no fix listed
- github.com/lxc/incus/v6 (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47753/ (Markdown: https://insights.sbomify.com/CVE-2026-47753/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47753
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47753
- OSV: https://osv.dev/vulnerability/CVE-2026-47753

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47753/
Summaries are generated and may contain mistakes; the official description above is the record.