Daemon crash via unchecked restored backup metadata
Published May 7, 2026 · Updated May 7, 2026
NULL pointer dereference in Incus before 7.0.0 allows remote authenticated users to crash the daemon via a crafted backup archive. ParseConfigYamlFile accepts restored legacy backup YAML without a container section, after which UpdateInstanceConfig and internalImportFromBackup dereference the nil Container field. Instance-backup import permission is required, and the resulting panic interrupts the daemon after archive extraction begins.
Summary
What happened
NULL pointer dereference in Incus before 7.0.0 allows remote authenticated users to crash the daemon via a crafted backup archive. ParseConfigYamlFile accepts restored legacy backup YAML without a container section, after which UpdateInstanceConfig and internalImportFromBackup dereference the nil Container field. Instance-backup import permission is required, and the resulting panic interrupts the daemon after archive extraction begins.
The record
- CVE
- CVE-2026-41684
- Published
- May 7, 2026
- Updated
- May 7, 2026
- Vendor
- Linux Containers
- Product
- Incus
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 7, 2026CVE publishedPublication date reported by the CVE source.
- May 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 7.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Extracted backup YAML panic testproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo