File Browser: Trailing-slash directory deletion leaves public shares active for recreated paths
CVE-2026-62683GHSA-pp88-jhwj-5qh5
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/filebrowser/filebrowser/v2 2.63.17), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/filebrowser/filebrowser/v2
- Affected
- < 2.63.17
- Fixed in
- 2.63.17
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-pp88-jhwj-5qh5 lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 <2.63.17
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-pp88-jhwj-5qh5 lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 <2.63.17 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2026-61874: 0.32% estimated exploitation activity in the next 30 days; percentile 24.80 (FIRST EPSS, 2026-11-14). This is a model estimate, not proof of exploitation or customer exposure.
- CVE-2026-62683: 0.32% estimated exploitation activity in the next 30 days; percentile 24.80 (FIRST EPSS, 2026-11-14). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary 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.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-pp88-jhwj-5qh5
- Revision 1 · created ·
Published from ghsa record GHSA-pp88-jhwj-5qh5
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-62683 Advisory: File Browser: Trailing-slash directory deletion leaves public shares active for recreated paths IDs: CVE-2026-62683, GHSA-pp88-jhwj-5qh5 Record: https://patchnext.com/advisories/cve-2026-62683 (revision 2, source checked 14 Nov 2026, 08:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 3.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/filebrowser/filebrowser/v2 2.63.17. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/filebrowser/filebrowser/v2: affected < 2.63.17; fixed in 2.63.17 ## Suggested inspection (read-only) - Go github.com/filebrowser/filebrowser/v2: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/filebrowser/filebrowser/v2. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-pp88-jhwj-5qh5 (GitHub-reviewed advisory GHSA-pp88-jhwj-5qh5 lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 <2.63.17) - Verified: https://osv.dev/vulnerability/GHSA-pp88-jhwj-5qh5 (OSV record GHSA-pp88-jhwj-5qh5 lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 <2.63.17 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…