CVE-2026-62683
LowCVSS 3.1Exploitation Probability (EPSS)
Low risk10th percentile - higher than 10% of all known CVEs
Summary
In File Browser before version 2.63.17, deleting a directory with a trailing slash (e.g., /a/) does not remove the existing public share for that directory (e.g., /a). The bug is caused by improper path normalization in the Bolt database query, leaving a stale share entry. Recreating the same directory re-exposes its content through the old share.
Risk Assessment
The organization risks unauthorized access to files placed in a recreated directory after the original was deleted. The stale public share may expose sensitive data to unintended parties.
Recommendation
Update File Browser to version 2.63.17 or later immediately. After updating, review and remove any stale public shares in the system.
Original NVD description (English source)
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.