Skip to main content
Menu
CVEs

CVE

Incus local VM disk hijack via exposed NBD sockets

Only affects Incus virtual machines before 7.6.0 while a VM migration or disk export is in progress; containers are not affected. Fixed in 7.6.0.

CVE-2026-130770Published Updated Summary written by a model

9.2CriticalCNA
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. A VM migration or disk export is in progress Only virtual machines are affected, not containers

Summary

Incus before 7.6.0 creates the NBD servers used for virtual machine migration and disk export on abstract unix sockets, which have no permission checks and whose names are visible in /proc/net/unix. A local unprivileged user can connect while an operation runs to read or modify the VM disk, gaining code execution in the guest on a migration's receiving side.

Who should check

Teams running Incus before v7.6.0 that run VM migrations or disk exports on hosts with untrusted local users

“Only virtual machines are affected; containers do not use these”

github.com

cve.now Index

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach10/20Affects Go packages
  • Severity9.2/10CVSS 9.2
  • No patch0/5No signal

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 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.

    A VM migration or disk export is in progress Only virtual machines are affected, not containers
  • 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-130770 (Incus before 7.6.0 VM Disk Hijacking via Abstract NBD Unix Sockets), 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-130770 (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):
- A VM migration or disk export is in progress (source: https://github.com/lxc/incus/security/advisories/GHSA-3rgf-297m-775x)
- Only virtual machines are affected, not containers (source: https://github.com/lxc/incus/security/advisories/GHSA-3rgf-297m-775x)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-130770 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130770 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-3rgf-297m-775x
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-130770
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-130770"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · lxc/incus · Advisory GHSA-3rgf-297m-775x
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130770
RecordNVD · CVE-2026-130770

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130770

Is CVE-2026-130770 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?

While a VM migration or disk export is in progress, a VM's disk can be read or modified. On the receiving side of a migration, control of the resulting VM's disk can lead to code execution inside that guest.Source: github.com

Which versions are affected by CVE-2026-130770?

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 virtual machines, not containers. The Incus version can be checked with the incus version command.Source: github.com

How do I fix CVE-2026-130770?

Upgrade Incus to 7.6.0 or later, which is the fixed version listed for this vulnerability.Source: github.com

More CVEs