# CVE-2026-130771: Incus before 7.6.0 Host File Read/Overwrite via Backup or Image Metadata


- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-130771, GHSA-5pgx-q9xx-j3qv, GHSA-fvq6-2fpv-cmcw, UBUNTU-CVE-2026-130771

## What is CVE-2026-130771?

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

### Official description

Incus before 7.6.0 fails to reject special files, hard links, or symlinks in backup or image metadata, allowing restricted project users to read or overwrite host files. Attackers can import crafted backups containing device nodes, a hard-linked backup.yaml, or symlinks to corrupt host storage, overwrite host files, or leak other projects' data.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

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

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

## Is CVE-2026-130771 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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