# CVE-2026-115378: Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 Arbitrary File Write via Recursive File Pull


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-115378, GHSA-38pq-92hw-9rp6, GHSA-wfvq-qh87-gm4j, UBUNTU-CVE-2026-115378

## What is CVE-2026-115378?

CVE-2026-115378 is a medium-severity vulnerability in lxc incus, published on 22 Oct 2026. 

### Official description

Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 contains an arbitrary file write vulnerability in sftpRecursivePullFile that allows a malicious incus-agent to escape the target directory during incus file pull -r. Attackers with root in a virtual machine can return duplicate entries reported first as symlinks then as files or directories, writing attacker-controlled files such as /etc/shadow on the operator's host.

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

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


## How do I fix CVE-2026-115378?

Upgrade to a fixed version.

## Is CVE-2026-115378 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115378 is a medium-severity vulnerability in lxc incus, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115378 in the wild and no public exploit code.

Affected product: lxc incus. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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