Incus has a Nil-Pointer Dereference Panic via Instance Backup Import (volume omitted)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-47753: 0.15% estimated exploitation activity in the next 30 days; percentile 4.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary (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): The caller createFromBackup in cmd/incusd/instancespost.go only verifies that Config and Config.Container are non-nil: 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…

Published by the source

10 Jun 2026, 20:07 UTC

Last modified by the source

10 Jun 2026, 20:07 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8g7m-96c8-8wwc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47753

Advisory: Incus has a Nil-Pointer Dereference Panic via Instance Backup Import (volume omitted)
IDs: CVE-2026-47753, GHSA-8g7m-96c8-8wwc
Record: https://patchnext.com/advisories/cve-2026-47753 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/lxc/incus/v7 7.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/lxc/incus/v7: affected < 7.1.0; fixed in 7.1.0

## Suggested inspection (read-only)
- Go github.com/lxc/incus/v7: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/lxc/incus/v7.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8g7m-96c8-8wwc (GitHub-reviewed advisory GHSA-8g7m-96c8-8wwc lists affected ranges: Go github.com/lxc/incus/v7 >=0 <7.1.0)

Commands are suggestions: review each one before running it.