CVE
Incus authorization bypass exposes default project resources
Affects Incus before 7.6.0 when a client holds a restricted or view-only certificate. 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. Client holds a restricted or view-only certificate
Summary
Incus before 7.6.0 contains an improper authorization vulnerability that allows restricted and view-only clients to read default project resources by requesting the default project directly. Attackers knowing resource names can read profiles, images, network zone peer keys and stored credentials, and export custom volume or bucket backups to obtain full contents or S3 admin keys.
Who should check
Teams running Incus before 7.6.0 that use restricted or view-only client certificates, including those with projects that inherit default-project resources.
“Restricted and view-only clients can read resources in the default project”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 33 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Client holds a restricted or view-only certificateUpgrade 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-130782 (Incus before 7.6.0 Improper Authorization Exposes Default Project Resources), 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-130782 (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):
- Client holds a restricted or view-only certificate (source: https://github.com/lxc/incus/security/advisories/GHSA-8r3h-vc36-6xpx)
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-130782 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130782 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-8r3h-vc36-6xpx
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-130782
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-130782"}.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-8r3h-vc36-6xpx |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130782 |
| Record | NVD · CVE-2026-130782 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130782
Is CVE-2026-130782 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 with a restricted or view-only certificate can read the configuration of profiles, images, custom volumes, buckets and network zones in the default project. That includes peer keys and stored credentials. The client can also download custom volume or bucket backups, which can expose full contents or S3 admin keys.Source: github.com
Which versions are affected by CVE-2026-130782?
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, and the issue needs a client that holds a restricted or view-only certificate. To check, run incus version to see the installed version, and review which client certificates are restricted or view-only.Source: github.com
How do I fix CVE-2026-130782?
Upgrade Incus to 7.6.0 or later, which is the fixed version.Source: github.com