CVE
Incus denial of service via null snapshot in backup import
Incus before 7.6.0 is affected: any client allowed to create instances in a project can crash the daemon with a crafted backup import. Fixed in 7.6.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 7.6.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Attacker must be a client allowed to create instances in a project. The backup's index.yaml snapshot list must contain an explicit null entry.
Summary
Incus before 7.6.0 contains a denial of service vulnerability that allows clients permitted to create instances to crash the daemon by importing a backup with a null snapshot entry in index.yaml. Attackers can trigger an unrecovered nil pointer dereference during configuration rewrite, terminating the daemon and all containers and virtual machines on the node.
Who should check
Operators running the Incus daemon (incusd) before v7.6.0, especially where users can create or import instances.
“github.com/lxc/incus/v7/cmd/incusd”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 32 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Attacker must be a client allowed to create instances in a project. The backup's index.yaml snapshot list must contain an explicit null entry.Upgrade to a fixed version: 7.6.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130769 (Incus before 7.6.0 Denial of Service via Null Snapshot Entry in Backup), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130769 (entry last updated 2026-11-18):
Affected:
- Go package github.com/lxc/incus/v7/cmd/incusd: fixed in 7.6.0
Fixed versions: 7.6.0.
Conditions (all must be true for the bug to be hit):
- Attacker must be a client allowed to create instances in a project. (source: https://github.com/lxc/incus/security/advisories/GHSA-x6pw-mh5w-pq73)
- The backup's index.yaml snapshot list must contain an explicit null entry. (source: https://github.com/lxc/incus/security/advisories/GHSA-x6pw-mh5w-pq73)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130769 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130769 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/lxc/incus/security/advisories/GHSA-x6pw-mh5w-pq73
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130769
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130769"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
fixed in 7.6.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · lxc/incus · Advisory GHSA-x6pw-mh5w-pq73 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130769 |
| Record | NVD · CVE-2026-130769 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130769
Is CVE-2026-130769 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A backup import whose index.yaml snapshot list contains an explicit null entry crashes the Incus daemon. The daemon terminates, taking down every container and virtual machine on the node until it is restarted.Source: github.com
Which versions are affected by CVE-2026-130769?
github.com/lxc/incus/v7/cmd/incusd (Go): before 7.6.0.Source: cve.now feed data
Am I affected, and how do I check?
Incus versions before 7.6.0 are listed as affected. The bug needs a client allowed to create instances in a project and a backup whose index.yaml snapshot list contains an explicit null entry; run incus version to check the installed version.Source: github.com
How do I fix CVE-2026-130769?
Upgrade Incus to 7.6.0 or later, the version the range lists as fixed. No vendor patch identifiers are given in the checked facts.Source: github.com