# CVE-2026-73693: FileRun < 2026.3.0 OS Command Injection via PhotoProofSheet Handler

> Authenticated users can execute arbitrary OS commands via malicious filenames in FileRun due to missing input sanitization in the PhotoProofSheet handler.

- **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:** 10 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-63rx-6h5r-6rfp

## What is CVE-2026-73693?

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

### Official description

FileRun before 2026.3.0 contains an OS command injection vulnerability in the PhotoProofSheet handler that allows authenticated users with upload permission to execute arbitrary commands by uploading files with shell metacharacters in their names. Attackers can upload a file containing command substitution syntax such as backticks, semicolons, or $() sequences in the filename, then trigger the PhotoProofSheet endpoint to execute arbitrary commands as the web-server user due to missing escapeshellarg() sanitization in the ImageMagick montage command construction.

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

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


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

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

## Is CVE-2026-73693 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73693 is a high-severity command injection vulnerability in FileRun, published on 10 Sep 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-73693 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-73693/ (Markdown: https://insights.sbomify.com/CVE-2026-73693/index.md)
```

## Sources

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

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