# CVE-2026-130786: Incus before 7.6.0 LXC Configuration Injection via OCI Image Config


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-130786, GHSA-3wxw-5gh2-j2x2, GHSA-62mw-4pw9-3hfc, UBUNTU-CVE-2026-130786

## What is CVE-2026-130786?

CVE-2026-130786 is a critical vulnerability in lxc incus, published on 18 Nov 2026. 

### Official description

Incus before 7.6.0 contains a configuration injection vulnerability that allows users who can launch instances from controlled images to inject LXC directives by embedding line breaks in OCI config.json values or oci.entrypoint and oci.cwd keys. Attackers can add liblxc hooks or crafted tmpfs lxc.mount.entry fields to run commands as root on the host or bind-mount host paths, even from restricted projects.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

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

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

## Is CVE-2026-130786 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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