Summary
File Browser: Trailing-slash directory deletion leaves public shares active for recreated paths
File Browser v2.63.15 can leave a public directory share behind when the shared directory is deleted through a path with a trailing slash. The share cleanup path calls DeleteWithPathPrefix(file.Path, userID), but the Bolt backend performs the database prefix query with the unnormalized argument before trimming the slash for boundary checks. For a stored share at /a, deleting /a/ queries for paths prefixed by /a/, so the exact /a share is never loaded and never deleted.
If a directory with the same path is later recreated, the stale public share becomes active again and exposes the new directory contents through the old public URL.
Reproduction
The following test was run against v2.63.15, commit be23ab3a15bf957928ecfed88de5ab67850c1b9c.
- Create a scoped user with share, download, and delete permissions.
- Create
/a/old.txtin that user's scope. - Store a valid public share row with
Hash: "h",UserID: 1, andPath: "/a". - Send an authenticated delete request for
/a/through the resource delete handler. - Confirm the directory is deleted.
- Confirm share hash
hstill exists in storage. - Recreate
/a/future.txt. - Request the public share handler at
h/and observe that the unauthenticated response includesfuture.txt.
Command used for the local proof:
go test ./http -run TestValidationTrailingSlashDeleteLeavesExactDirectoryShare -count=1 -v
Observed result:
=== RUN TestValidationTrailingSlashDeleteLeavesExactDirectoryShare
--- PASS: TestValidationTrailingSlashDeleteLeavesExactDirectoryShare (0.03s)
PASS
ok github.com/filebrowser/filebrowser/v2/http 0.044s
Root cause
storage/bolt/share.go queries the share index before normalizing the path:
func (s shareBackend) DeleteWithPathPrefix(pathPrefix string, userID uint) error {
var links []share.Link
if err := s.db.Prefix("Path", pathPrefix, &links); err != nil {
...
}
prefix := strings.TrimRight(pathPrefix, "/")
for _, link := range links {
if link.UserID != userID {
continue
}
if link.Path != prefix && !strings.HasPrefix(link.Path, prefix+"/") {
continue
}
...
}
}
For pathPrefix == "/a/", the database prefix query can return descendants such as /a/child, but it does not return the exact share path /a. The later TrimRight cannot delete the exact share because that row was not loaded from storage.
http/resource.go passes the request-derived path into this cleanup before removing the resource:
file, err := files.NewFileInfo(... Path: r.URL.Path ...)
...
err = d.store.Share.DeleteWithPathPrefix(file.Path, d.user.ID)
...
return d.user.Fs.RemoveAll(r.URL.Path)
A request for /a/ therefore removes the directory but misses the exact /a share row.
Impact
An authenticated user with share, download, and delete permissions can create a valid public share, delete the shared path with a trailing slash, and leave the public link in storage. The link is dormant while the path does not exist, but it exposes future content if the same path is recreated later. The final data exposure is unauthenticated through the public share URL.
This bypasses the intended lifecycle cleanup around public shares and is adjacent to the recent public-share path-existence and prefix-boundary fixes.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
CVE-2026-62683 has a CVSS score of 3.1 (Low). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.63.17); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Normalize the path before querying the share index, and cover both the exact normalized path and its descendants. Add regression tests where a stored share path /a is removed by DeleteWithPathPrefix("/a/", userID) and where DELETE /api/resources/a/ deletes the exact public share row.
Fixed in version 2.63.17.
Frequently Asked Questions
- What is CVE-2026-62683? CVE-2026-62683 is a low-severity incorrect authorization vulnerability in github.com/filebrowser/filebrowser/v2 (go), affecting versions < 2.63.17. It is fixed in 2.63.17. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- How severe is CVE-2026-62683? CVE-2026-62683 has a CVSS score of 3.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/filebrowser/filebrowser/v2 are affected by CVE-2026-62683? github.com/filebrowser/filebrowser/v2 (go) versions < 2.63.17 is affected.
- Is there a fix for CVE-2026-62683? Yes. CVE-2026-62683 is fixed in 2.63.17. Upgrade to this version or later.
- Is CVE-2026-62683 exploitable, and should I be worried? Whether CVE-2026-62683 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-62683 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-62683? Upgrade
github.com/filebrowser/filebrowser/v2to 2.63.17 or later.