# CVE-2026-82237: filebrowser through 2.63.23 Stale Share Link via File Rename

> Attackers can access unrelated files via stale share links if files are renamed, exposing data unexpectedly in filebrowser.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/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:** No
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-m8v4-4w34-rrvf, GHSA-v6g4-hccq-frhr

## What is CVE-2026-82237?

CVE-2026-82237 is a low-severity vulnerability in filebrowser, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

filebrowser through 2.63.23 does not remove share records when a shared file is renamed (only deletion triggers share cleanup). The share record is keyed by path, so it survives the rename and remains dormant (returning 404 while the path is empty). When any new, unrelated file later appears at the original shared path — via re-upload, another user with create permission, or a hook — the stale public share link serves that new file under the original link's password and expiry settings, unexpectedly exposing it.

Weakness: CWE-459 (Incomplete Cleanup)

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


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

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

## Is CVE-2026-82237 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82237 is a low-severity vulnerability in filebrowser, published on 28 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-82237 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-82237/ (Markdown: https://insights.sbomify.com/CVE-2026-82237/index.md)
```

## Sources

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

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