# CVE-2026-44542: FileBrowser Quantum: Unauthenticated Path Traversal in Public Share Delete Allows Arbitrary File Deletion

> Unauthenticated attackers with a valid share hash can delete arbitrary files outside the shared directory due to improper path sanitization.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-fwj3-42wh-8673, GO-2026-5383

## What is CVE-2026-44542?

CVE-2026-44542 is a critical path traversal vulnerability in gtsteffaniak filebrowser, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FileBrowser Quantum is a free, self-hosted, web-based file manager. Prior to 1.3.1-stable and 1.3.9-beta, attacker-controlled path input is joined with a trusted base path prior to sanitization, allowing traversal sequences (e.g., ../) to escape the intended shared directory. As a result, an unauthenticated attacker possessing a valid public share hash with delete permissions enabled can delete arbitrary files outside the shared directory within the share owner’s configured storage scope. This affects public/api/resources and public/api/resources/bulk. This vulnerability is fixed in 1.3.1-stable and 1.3.9-beta.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including github.com/gtsteffaniak/filebrowser. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gtsteffaniak/filebrowser` | Go | All versions | 0.0.0-20260501183844-112740bdd41d |
| `github.com/gtsteffaniak/filebrowser` | Go | All versions | 0.0.0-20260501183844-112740bdd41d |
| `github.com/gtsteffaniak/filebrowser` | Go | All versions | 0.0.0-20260501183844-112740bdd41d |

Products: Gtsteffaniak Filebrowser Quantum.

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

Upgrade github.com/gtsteffaniak/filebrowser to 0.0.0-20260501183844-112740bdd41d or later.

## Is CVE-2026-44542 being exploited?

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

## Other vulnerabilities in gtsteffaniak filebrowser

- [CVE-2026-27611](https://insights.sbomify.com/CVE-2026-27611/): FileBrowser Quantum: Password Protection Not Enforced on Shared File Links (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44542 is a critical path traversal vulnerability in gtsteffaniak filebrowser, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44542 exists.

Affected packages and fixed versions:
- github.com/gtsteffaniak/filebrowser (Go): affected all versions; fixed in 0.0.0-20260501183844-112740bdd41d
- github.com/gtsteffaniak/filebrowser (Go): affected all versions; fixed in 0.0.0-20260501183844-112740bdd41d
- github.com/gtsteffaniak/filebrowser (Go): affected all versions; fixed in 0.0.0-20260501183844-112740bdd41d

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

## Sources

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

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