Is CVE-2026-47753 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47753 being exploited in the wild.

How severe is CVE-2026-47753?

Medium severity, with a CVSS score of 4, published 21 August 2026.

Which products and versions are affected?

github.com/lxc/incus (Go) SEMVER:introduced=0; github.com/lxc/incus/v6 (Go) SEMVER:introduced=0; github.com/lxc/incus/v7 (Go) < 7.1.0, SEMVER:introduced=0,fixed=7.1.0; Linux Containers Project Incus < 7.1.0.

Is there a fix for CVE-2026-47753?

Yes. github.com/lxc/incus/v7 (Go): upgrade to 7.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47753 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-47753?

Check whether you run github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47753: LXC Incus nil-pointer dereference in CreateInstanceFromBackup

Q: Is there a fix for CVE-2026-47753?

Yes. github.com/lxc/incus/v7 (Go): upgrade to 7.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-47753 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2026-47753?

Check whether you run github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47753 · Severity: medium · CVSS 4 · Published 2026-08-21

Incus, a container and virtual machine management tool, is vulnerable to a denial-of-service attack. An authenticated user can crash the management daemon by uploading a specially crafted backup file that is missing specific volume information. This crash stops all ongoing container and VM operations on the affected server and prevents new requests until the service is manually restarted.

Technologies: github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go), Linux Containers Project Incus. Vendors: Go, Linux Containers Project.

Quick answers

Is CVE-2026-47753 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47753 being exploited in the wild.
How severe is CVE-2026-47753?: Medium severity, with a CVSS score of 4, published 21 August 2026.
Which products and versions are affected?: github.com/lxc/incus (Go) SEMVER:introduced=0; github.com/lxc/incus/v6 (Go) SEMVER:introduced=0; github.com/lxc/incus/v7 (Go) < 7.1.0, SEMVER:introduced=0,fixed=7.1.0; Linux Containers Project Incus < 7.1.0.
Is there a fix for CVE-2026-47753?: Yes. github.com/lxc/incus/v7 (Go): upgrade to 7.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47753 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-47753?: Check whether you run github.com/lxc/incus (Go), github.com/lxc/incus/v6 (Go), github.com/lxc/incus/v7 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/lxc/incus/v7 (Go): upgrade to 7.1.0 or later
```
go get github.com/lxc/incus/v7@v7.1.0
```

Technical details

A nil-pointer dereference exists in the `(*backend).CreateInstanceFromBackup` function within `internal/server/storage/backend.go`. The vulnerability is triggered when the `Volume` field in a backup's `index.yaml` is omitted, causing the Go runtime to encounter a nil pointer when attempting to access `srcBackup.Config.Volume.Config`. An attacker with 'can_create' permissions in any project can exploit this by performing a POST request to the `/1.0/instances` endpoint with a crafted tarball. Because the daemon does not implement a recovery mechanism for this panic, the entire `incusd` process terminates, resulting in a complete denial of service for the cluster member. The issue is fixed in version 7.1.0.

Affected products

LXC Incus < 7.1.0

Identifiers

CVE-2026-47753
GHSA-8g7m-96c8-8wwc
GO-2026-5252

Timeline

2026-05-28: disclosed
2026-05-28: patched
2026-06-10: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.