# CVE-2026-130773: Incus before 7.6.0 Project Isolation Bypass via Default Project Resource Creation


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-130773, GHSA-j6g2-8h27-wpfx, GHSA-jcw9-v2ff-8m79, UBUNTU-CVE-2026-130773

## What is CVE-2026-130773?

CVE-2026-130773 is a critical vulnerability in lxc incus, published on 18 Nov 2026. 

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-130773?

1 open source package ship an affected version, including github.com/lxc/incus/v7/cmd/incusd.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `github.com/lxc/incus/v7/cmd/incusd` | Go | `pkg:golang/github.com/lxc/incus/v7/cmd/incusd` | All versions | 7.6.0 |

## How do I fix CVE-2026-130773?

Upgrade github.com/lxc/incus/v7/cmd/incusd to 7.6.0 or later.

## Is CVE-2026-130773 being exploited?

There is no known exploitation of CVE-2026-130773 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130773 and fix it if it is affected.

What it is: CVE-2026-130773 is a critical vulnerability in lxc incus, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130773 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/lxc/incus/v7/cmd/incusd (Go): affected all versions; fixed in 7.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130773/ (Markdown: https://insights.sbomify.com/CVE-2026-130773/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130773
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130773
- OSV: https://osv.dev/vulnerability/CVE-2026-130773

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130773/
Summaries are generated and may contain mistakes; the official description above is the record.
