# CVE-2026-130775: Incus before 7.6.0 Cross-Project Image Disclosure via /dev/incus Image Export


- **Severity:** High 8.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/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-130775, GHSA-f7xp-22ph-v444, GHSA-ffq6-h959-h2qp, UBUNTU-CVE-2026-130775

## What is CVE-2026-130775?

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

### Official description

Incus before 7.6.0 contains an authorization bypass vulnerability in the /dev/incus guest-API image export handler that fails to pin the project parameter to the guest's own project. Container root users with the guest-API image entitlement can supply another project in the project query parameter to export public or cached images, including non-public images pulled from authenticated remotes.

Weakness: CWE-863 (Incorrect Authorization)

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

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

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

## Is CVE-2026-130775 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130775 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130775 is a high-severity vulnerability in lxc incus, published on 18 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130775 exists.

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-130775/ (Markdown: https://insights.sbomify.com/CVE-2026-130775/index.md)
```

## Sources

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

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