CVE
Incus path traversal in migration dependent volumes
Affects Incus before 7.6.0 when an instance with dependent custom volumes is received through migration from a peer. 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. Incus versions before 7.6.0 Instance received through migration from a peer, with dependent custom volumes
Summary
Incus before 7.6.0 contains a path traversal vulnerability that allows malicious migration peers to write outside intended directories by supplying unvalidated dependent volume and snapshot names in the migration offer header. Attackers controlling a migration source can create root-owned volumes with attacker content at arbitrary host paths, compromising hosts using dir storage pools, bypassing restricted.storage-pools.access, or crashing the daemon.
Who should check
Teams running Incus (incusd, Go) that receive instance migrations from other servers, especially those using dir storage pools
“Affected versions < v7.6.0”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity9.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 34 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Incus versions before 7.6.0 Instance received through migration from a peer, with dependent custom volumesUpgrade 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-130780 (Incus before 7.6.0 Path Traversal via Dependent Volumes in Migration), 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-130780 (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):
- Incus versions before 7.6.0 (source: https://github.com/lxc/incus/security/advisories/GHSA-q9fc-p923-6vp7)
- Instance received through migration from a peer, with dependent custom volumes (source: https://github.com/lxc/incus/security/advisories/GHSA-q9fc-p923-6vp7)
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-130780 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130780 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-q9fc-p923-6vp7
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-130780
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-130780"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
fixed in 7.6.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · lxc/incus · Advisory GHSA-q9fc-p923-6vp7 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130780 |
| Record | NVD · CVE-2026-130780 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130780
Is CVE-2026-130780 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?
When Incus receives an instance through migration, it uses the names of the instance's dependent custom volumes and their snapshots as path segments without validating them. A malicious migration source can therefore make the target create a root-owned volume at an arbitrary host path and fill it with attacker-controlled content.Source: github.com
Which versions are affected by CVE-2026-130780?
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 affected, but only when an instance with dependent custom volumes is received through migration, such as a copy or move from a peer. Check the installed version with the incus version command.Source: github.com
How do I fix CVE-2026-130780?
Upgrade Incus to 7.6.0 or later, which is the fixed version for this vulnerability.Source: github.com