Advisory record · GHSA-5ww9-jg6q-38r7

File Browser: Cross-user unauthorized share-link deletion via unbounded prefix match in DeleteWithPathPrefix

CVSS 7.2 HighEPSS 0.0045 · 39th percentile

Published by the GitHub Advisory Database at 12 Jun 2026, 21:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/filebrowser/filebrowserGo<=1.11.0No fixed version yet
github.com/filebrowser/filebrowser/v2Go<2.63.62.63.6
Identifiers
GHSA-5ww9-jg6q-38r7 · CVE-2026-54097 · GO-2026-5159
Weakness (CWE)
CWE-639
Published
12 Jun 2026
Updated
21 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Filebrowser versions up to and including 1.11.0 (Go module github.com/filebrowser/filebrowser) and versions before 2.63.6 of github.com/filebrowser/filebrowser/v2 are affected. An authenticated user with create and delete permissions can delete a file whose path is a prefix of another user's share link path, which silently removes that other user's share links, including administrators' links. The source gives few details on the exact trigger conditions. Upgrade the v2 module to 2.63.6; no fixed version is listed for the unversioned module.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.2 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0045, the 39th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.