# CVE-2026-130772: Incus before 7.6.0 Information Disclosure via Recursive and All-Projects Responses


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-130772, GHSA-pf5w-m8m6-5265, GHSA-vcpg-fg5m-wx72, UBUNTU-CVE-2026-130772

## What is CVE-2026-130772?

CVE-2026-130772 is a high-severity vulnerability in lxc incus, published on 18 Nov 2026. 

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

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

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-130772?

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

## Is CVE-2026-130772 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130772 is a high-severity vulnerability in lxc incus, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130772 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-130772/ (Markdown: https://insights.sbomify.com/CVE-2026-130772/index.md)
```

## Sources

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

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