CVE-2026-62683 File Browser: Trailing-slash delete leaves a stale public share behind
Attackers can access future content in recreated directories because stale public shares persist after deletion via trailing-slash paths.
- 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-62683?
CVE-2026-62683 is a low-severity missing authorization vulnerability in filebrowser, published on 15 Jul 2026. Any signed-in user can exploit it over the network, 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. Prior to 2.63.17, File Browser can leave a public directory share behind when the shared directory is deleted through a path with a trailing slash because the share cleanup path calls DeleteWithPathPrefix(file.Path, userID) and the Bolt backend performs the database prefix query with the unnormalized path before trimming the slash for boundary checks, so deleting /a/ does not delete the stored /a share and the stale public share exposes future content if the same path is recreated. This issue is fixed in version 2.63.17.
Weakness: CWE-863
Which versions are affected by CVE-2026-62683?
How do I fix CVE-2026-62683?
No fix has been published for CVE-2026-62683 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-62683 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62683 exists.