CVE
Incus root code execution via project isolation bypass
Affects Incus before 7.6.0 when a project lacks the relevant features flag and a client certificate is restricted to one project with only create rights there. 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. The project lacks the relevant features.* flag, so the effective project is default Client certificate restricted to a single project, holding only a create entitlement on that project
Summary
Incus before 7.6.0 contains an authorization bypass that allows restricted project users to create resources in the unrestricted default project by targeting projects lacking features.* flags. Attackers can create bridge networks with raw.dnsmasq dhcp-script injection to run scripts as root, or custom volumes with block.create_options mkfs arguments to read host files.
Who should check
Teams running Incus before 7.6.0 with restricted projects, restricted certificates, or tenant users who can create networks or storage volumes
“Restricted project users can create resources in the default project, bypassing project isolation”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity10/10CVSS 9.4, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 78 if added to CISA KEV
- Would score about 73 if CISA's SSVC rates exploitation active
- Would score about 35 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The project lacks the relevant features.* flag, so the effective project is default Client certificate restricted to a single project, holding only a create entitlement on that projectUpgrade 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-130773 (Incus before 7.6.0 Project Isolation Bypass via Default Project Resource Creation), 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-130773 (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):
- The project lacks the relevant features.* flag, so the effective project is default (source: https://github.com/lxc/incus/security/advisories/GHSA-jcw9-v2ff-8m79)
- Client certificate restricted to a single project, holding only a create entitlement on that project (source: https://github.com/lxc/incus/security/advisories/GHSA-jcw9-v2ff-8m79)
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-130773 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130773 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-jcw9-v2ff-8m79
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-130773
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-130773"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- 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-jcw9-v2ff-8m79 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130773 |
| Record | NVD · CVE-2026-130773 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130773
Is CVE-2026-130773 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 client certificate restricted to one project and holding only a create entitlement there can create bridge networks or custom volumes in the default project. The advisory says this can lead to root code execution on the host via dnsmasq, or host file disclosure via mkfs arguments.Source: github.com
Which versions are affected by CVE-2026-130773?
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 where the project lacks the relevant features flag, so the effective project is default. The setup also needs a client certificate restricted to a single project with only a create entitlement on that project. Check the Incus version with the version command, and check the project's features settings.Source: github.com
How do I fix CVE-2026-130773?
Upgrade Incus to 7.6.0 or later, which is the listed fixed version.Source: github.com