CVE
Incus info disclosure in migration websocket secrets
Affects Incus before 7.6.0 when a migration is in progress in a project where a client holds event-view access. No vendor severity is given beyond the CVSS score of 7.1. 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. A client holds project event-view access (can_view_events) on the project running the migration An instance, volume or snapshot migration is in progress
Summary
Incus before 7.6.0 contains an information disclosure vulnerability that allows clients with project event-view access to read migration websocket secrets broadcast in operation metadata. Attackers can connect to in-flight migration control and fs websockets before the legitimate peer, hijacking the transfer to obtain instance configuration and filesystem data.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- 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.
A client holds project event-view access (can_view_events) on the project running the migration An instance, volume or snapshot migration is in progressUpgrade 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-130776 (Incus before 7.6.0 Migration Hijack via Exposed Websocket Secrets), 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-130776 (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 client holds project event-view access (can_view_events) on the project running the migration (source: https://github.com/lxc/incus/security/advisories/GHSA-h2j8-4crh-vhfc)
- An instance, volume or snapshot migration is in progress (source: https://github.com/lxc/incus/security/advisories/GHSA-h2j8-4crh-vhfc)
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-130776 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130776 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-h2j8-4crh-vhfc
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-130776
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-130776"}.Timeline
- CVE published
- First seen 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-h2j8-4crh-vhfc |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130776 |
| Record | NVD · CVE-2026-130776 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130776
Is CVE-2026-130776 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?
Instance, volume and snapshot migrations embed per-connection websocket secrets in the operation metadata, and that metadata is broadcast to every event listener with view access on the operation's project. An attacker with event-view access to a project can capture these secrets, hijack the migration's data websockets, and receive the instance configuration and filesystem data for an instance they may not otherwise be able to read.Source: github.com
Which versions are affected by CVE-2026-130776?
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, in setups where a migration is in progress and a client holds can_view_events on the project running it. To check the Incus version, a reader can run the incus version command, and to check the access setting, a reader can review which clients hold can_view_events on the project.Source: github.com
How do I fix CVE-2026-130776?
Upgrade Incus to 7.6.0 or later, which is the fixed version listed for this vulnerability. The sources do not name a workaround or separate vendor patch identifiers.Source: github.com