CVE
Incus authorization bypass in default project resource checks
Only affects Incus before 7.6.0 with restricted clients limited to a project that has features.networks disabled, the default for new projects. No vendor rating is given. 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. Affects Incus versions before 7.6.0. Client is a restricted client (restricted certificate) limited to a project with the matching features.* key disabled, such as features.networks disabled, which is the default for new projects.
Summary
Incus before 7.6.0 contains an authorization bypass vulnerability that allows restricted clients to create and access default project resources by exploiting entitlement checks against the requested project. Attackers can create bridge networks with raw.dnsmasq directives to execute code as root on the host, or manipulate inherited resources via the ?project= parameter.
Who should check
Teams running Incus (lxc/incus) before 7.6.0 with restricted client certificates and projects that have features.* keys disabled, such as features.networks; Go teams depending on cmd/incusd.
“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.
Affects Incus versions before 7.6.0. Client is a restricted client (restricted certificate) limited to a project with the matching features.* key disabled, such as features.networks disabled, which is the default for new projects.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-130784 (Incus before 7.6.0 Authorization Bypass via Default Project Resource Inheritance), 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-130784 (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):
- Affects Incus versions before 7.6.0. (source: https://github.com/lxc/incus/security/advisories/GHSA-5c64-j5m6-8433)
- Client is a restricted client (restricted certificate) limited to a project with the matching features.* key disabled, such as features.networks disabled, which is the default for new projects. (source: https://github.com/lxc/incus/security/advisories/GHSA-5c64-j5m6-8433)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130784 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130784 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-5c64-j5m6-8433
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-130784
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-130784"}.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-5c64-j5m6-8433 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130784 |
| Record | NVD · CVE-2026-130784 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130784
Is CVE-2026-130784 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 restricted client limited to one project can create networks, network ACLs, address sets and other resources in the default project. Via bridge networks with raw.dnsmasq directives, this can lead to code execution as root on the host. It can also read, update, rename or delete inherited resources and read another project's network DHCP leases through the ?project= parameter.Source: github.com
Which versions are affected by CVE-2026-130784?
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 a restricted client is limited to a project with features.networks disabled, which is the default for new projects. Check your Incus version with the incus version command and check each project's features.networks setting with incus project show.Source: github.com
How do I fix CVE-2026-130784?
Upgrade Incus to version 7.6.0 or later, which is the fixed version.Source: github.com