CVE
Incus authorization bypass in bucket and profile listings
Affects Incus before 7.6.0 for restricted TLS clients with view access to a storage bucket, and for listing requests sent with all-projects=true. 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. Restricted TLS client that has view access to a storage bucket. Listing requests sent with all-projects=true, such as profile or bucket listings.
Summary
Incus before 7.6.0 contains an improper authorization vulnerability that allows restricted TLS clients to read other projects' bucket S3 keys and profile configuration through recursive and all-projects responses. Attackers can query bucket listings with recursion=2 or profiles with all-projects=true to obtain S3 secret keys and sensitive environment, cloud-init and user values across projects.
Who should check
Teams running Incus incusd before 7.6.0 with storage buckets, or multi-project setups using restricted TLS client certificates.
“github.com/lxc/incus/v7/cmd/incusd”
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.
Restricted TLS client that has view access to a storage bucket. Listing requests sent with all-projects=true, such as profile or bucket listings.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-130772 (Incus before 7.6.0 Information Disclosure via Recursive and All-Projects Responses), 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-130772 (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):
- Restricted TLS client that has view access to a storage bucket. (source: https://github.com/lxc/incus/security/advisories/GHSA-pf5w-m8m6-5265)
- Listing requests sent with all-projects=true, such as profile or bucket listings. (source: https://github.com/lxc/incus/security/advisories/GHSA-pf5w-m8m6-5265)
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-130772 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130772 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-pf5w-m8m6-5265
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-130772
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-130772"}.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-pf5w-m8m6-5265 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130772 |
| Record | NVD · CVE-2026-130772 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130772
Is CVE-2026-130772 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 TLS client that can only view a storage bucket can read the configuration of buckets in every project, and with recursion=2 can also read their S3 access and secret keys. Listing requests with all-projects=true, such as profile listings, return profiles from every project, including sensitive environment, cloud-init and user values.Source: github.com
Which versions are affected by CVE-2026-130772?
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 that use restricted TLS clients with view access to a storage bucket, and in listing requests sent with all-projects=true, such as profile or bucket listings. The installed version can be checked with the incus version command.Source: github.com
How do I fix CVE-2026-130772?
Upgrade Incus to 7.6.0 or later, which is the fixed version for this vulnerability.Source: github.com