# CVE-2026-73612: File Browser before v2.63.22 Authorization Bypass via Recursive Operations

> Authenticated users can bypass path-based access controls to read, modify, or delete restricted files via recursive operations on parent directories.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/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:** Yes
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-77x8-73f4-5485, GHSA-wx2x-g9fw-53fc, MINI-2jwc-w336-v8j4, MINI-v345-2fgj-qj8g

## What is CVE-2026-73612?

CVE-2026-73612 is a high-severity missing authorization vulnerability in filebrowser, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

File Browser before v2.63.22 fails to validate access rules for descendants during recursive copy, rename, and delete operations, allowing authenticated users to bypass path-based access controls. Attackers can copy, rename, or delete denied files by operating on their allowed parent directory, defeating rule-based isolation for confidentiality and integrity.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

Upgrade to a fixed version.

## Is CVE-2026-73612 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73612 is a high-severity missing authorization vulnerability in filebrowser, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73612 exists.

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

## Sources

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

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