CVE-2026-47753 lxc CVE debrief

Who should care

Users of Incus versions prior to 7.1.0, administrators of systems using Incus for container and virtual machine management, and security teams responsible for vulnerability management and incident response.

Technical summary

A nil-pointer dereference in Incus versions prior to 7.1.0 allows authenticated users with instance creation permissions to trigger a denial-of-service condition. This issue 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.

Defensive priority

Authenticated users with instance creation permissions can trigger a denial-of-service condition; verify instance creation access controls and monitor for unusual backup uploads.

Recommended defensive actions

• Verify instance creation access controls
• Monitor for unusual backup uploads
• Update to Incus version 7.1.0 or later
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Review compensating controls for exposed systems while remediation is scheduled and verified.

Evidence notes

The CVE record indicates a nil-pointer dereference in Incus version prior to 7.1.0; verify installed version and apply patches if necessary. This issue allows authenticated users with instance creation permissions to trigger a denial-of-service condition. Verify instance creation access controls and monitor for unusual backup uploads. Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.