# CVE-2026-35585: File Browser has a Command Injection via Hook Runner

> An attacker with file write permissions can execute arbitrary OS commands via malicious filenames in the hook system, requiring the feature to be enabled.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Apr 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-jvpw-637p-h3pw, GO-2026-5481

## What is CVE-2026-35585?

CVE-2026-35585 is a high-severity command injection vulnerability in filebrowser, published on 7 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. From 2.0.0 until 2.33.8, the hook system in File Browser — which executes administrator-defined shell commands on file events such as upload, rename, and delete — is vulnerable to OS command injection. Variable substitution for values like $FILE and $USERNAME is performed via os.Expand without sanitization. An attacker with file write permission can craft a malicious filename containing shell metacharacters, causing the server to execute arbitrary OS commands when the hook fires. This results in Remote Code Execution (RCE). This feature has been disabled by default for all installations from v2.33.8 onwards, including for existent installations.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

4 open source packages ship an affected version, including github.com/filebrowser/filebrowser/v2 and github.com/filebrowser/filebrowser. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.33.8 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.33.8 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.33.8 |
| `github.com/filebrowser/filebrowser` | Go | All versions | None |

Products: Filebrowser Filebrowser.

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

Upgrade github.com/filebrowser/filebrowser/v2 to 2.33.8 or later.

## Is CVE-2026-35585 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35585 exists.

Public exploit code:

- https://github.com/Saku0512/CVE-2026-35585-poc (github_poc): https://github.com/Saku0512/CVE-2026-35585-poc

## Other vulnerabilities in filebrowser

- [CVE-2026-32760](https://insights.sbomify.com/CVE-2026-32760/): File Browser Self Registration Grants Any User Admin Access When Default Permissions Include Admin (critical 10.0)
- [CVE-2026-29188](https://insights.sbomify.com/CVE-2026-29188/): File Browser: TUS Delete Endpoint Bypasses Delete Permission Check (critical 9.1)
- [CVE-2023-39612](https://insights.sbomify.com/CVE-2023-39612/): Cross-site scripting in n/a (critical 9.0)
- [CVE-2026-30934](https://insights.sbomify.com/CVE-2026-30934/): FileBrowser Quantum: Stored XSS in public share page via unsanitized share metadata (text/template misuse) (high 8.9)
- [CVE-2021-46398](https://insights.sbomify.com/CVE-2021-46398/): Cross-Site Request Forgery in Filebrowser (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35585 is a high-severity command injection vulnerability in filebrowser, published on 7 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35585 exists.

Affected packages and fixed versions:
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.33.8
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.33.8
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.33.8
- github.com/filebrowser/filebrowser (Go): affected all versions; no fix listed

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

## Sources

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

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