File Browser: Improper Access Control Occurs via Pre-Created Public Share for a Non-existent Path

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-54096: 0.18% estimated exploitation activity in the next 30 days; percentile 7.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary This is similar vulnrability of CVE-2026-0035, which was fixed in Android MediaProvider with high severity. In the original Java issue, MediaStore.createWriteRequest() accepted attacker-controlled URIs and created a future grant even when the referenced media item did not exist yet. The Android fix added an existence check before creating the request. filebrowser/filebrowser has the analogous issue in Go. POST /api/share/<path accepts an authenticated request for an arbitrary path and stores a public share record without checking whether the target file currently exists. Later, when a file is created at that same path, the previously created public share immediately becomes valid and exposes the new file through GET /api/public/dl/<hash. Details The vulnerable create path is: - http/share.go - sharePostHandler() - route: POST /api/share/<path sharePostHandler() only checks that the caller is authenticated and has share/download permissions. It then builds a share.Link…

Published by the source

12 Jun 2026, 21:07 UTC

Last modified by the source

21 Jul 2026, 14:45 UTC

Source last checked

26 Oct 2026, 15:27 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3q2p-72cj-682c

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54096

Advisory: File Browser: Improper Access Control Occurs via Pre-Created Public Share for a Non-existent Path
IDs: CVE-2026-54096, GHSA-3q2p-72cj-682c
Record: https://patchnext.com/advisories/cve-2026-54096 (revision 1, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/filebrowser/filebrowser/v2 2.63.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/filebrowser/filebrowser/v2: affected <= 2.63.6; fixed in 2.63.7
- Go github.com/filebrowser/filebrowser: affected <= 1.11.0

## Suggested inspection (read-only)
- Go github.com/filebrowser/filebrowser/v2: check the installed version with your package manager.
- Go github.com/filebrowser/filebrowser: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/filebrowser/filebrowser/v2, github.com/filebrowser/filebrowser.
- 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-3q2p-72cj-682c (GitHub-reviewed advisory GHSA-3q2p-72cj-682c lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 =0 <=1.11.0)

Commands are suggestions: review each one before running it.