# 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.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A: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:** 15 Jul 2026
- **Updated:** 15 Jul 2026

## 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 (Incorrect Authorization)

## 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.

## Is CVE-2026-62683 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62683 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-62683/ (Markdown: https://insights.sbomify.com/CVE-2026-62683/index.md)
```

## Sources

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

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