# CVE-2026-73680: Cockpit CMS 2.14.0 Authenticated Command Injection via FFmpeg Filename

> Authenticated users with upload permissions can execute arbitrary commands via malicious filenames in Cockpit CMS due to unsanitized input in FFmpeg integration.

- **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:** 14 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-4x4q-mx3g-g3m2

## What is CVE-2026-73680?

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

### Official description

Cockpit CMS 2.14.0 and prior contains a command injection vulnerability in the FFmpeg integration that allows authenticated users with only the assets/upload permission to execute arbitrary commands by uploading a video file with a shell metacharacter-laden filename. The unsanitized filename is interpolated into a shell command executed via Process::fromShellCommandline() before the slugify() sanitizer runs, enabling injected shell metacharacters such as backticks, $(), and semicolons to escape the FFmpeg command context and execute as the web-server user.

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

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


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

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

## Is CVE-2026-73680 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73680 is a high-severity command injection vulnerability in Cockpit CMS, published on 14 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-73680 in the wild and no public exploit code.

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

## Sources

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

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