# CVE-2026-14863: FileRun 2026.2.0 RCE via Thumbnail Generation Command Injection

> Authenticated attackers can execute arbitrary commands by uploading files with malicious filenames that trigger command injection during thumbnail generation.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-mcfq-hmcc-5pch

## What is CVE-2026-14863?

CVE-2026-14863 is a high-severity command injection vulnerability in FileRun, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FileRun up to and including version 2026.2.0 contains an OS command injection vulnerability that allows authenticated attackers to achieve remote code execution by uploading a file with a malicious filename containing shell command substitution sequences. The thumbnail generation system passes filenames wrapped in shell double-quotes directly to exec() without escapeshellarg() sanitization, allowing filenames such as $(PAYLOAD).mp4 to survive the filename sanitizer and be evaluated as shell commands when ffmpeg, ImageMagick, vips, or stl-thumb processes the file during thumbnail generation.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

No fix has been published for CVE-2026-14863 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14863 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14863 is a high-severity command injection vulnerability in FileRun, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14863 in the wild and no public exploit code.

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

## Sources

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

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