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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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
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.
Sources
Also known as GHSA-m8v4-4w34-rrvf, GHSA-v6g4-hccq-frhr.