CVE-2026-61874: filebrowser before 2.63.17 Stale Public Share via Trailing-Slash Delete
filebrowser versions before 2.63.17 fail to normalize paths before querying the share index in DeleteWithPathPrefix, allowing authenticated users to leave stale public shares behind. Attackers can delete a shared directory using a trailing-slash path, then recreate the same directory to expose new contents through the dormant public share URL.
Security readout for executives and security teams
Plain-English summary
CVE-2026-61874 is a low-severity filebrowser issue where public share links can remain active after a shared folder is deleted in a specific path-handling case. If that folder is recreated, the old public link may expose new contents. This is mainly a confidentiality risk for organizations using filebrowser public shares.
Executive priority
Treat as a routine but timely fix if filebrowser public shares are used. Prioritize systems exposing shared files externally or handling sensitive data. The business risk is accidental disclosure through old public links, not broad system compromise.
Technical view
filebrowser before 2.63.17 does not normalize paths before querying the share index in DeleteWithPathPrefix. An authenticated user can cause public share cleanup to miss a matching path when deletion uses a trailing slash. Recreating the same directory can make new contents reachable through the dormant public share URL. CVSS is 3.1, confidentiality low.
Likely exposure
Exposure is limited to filebrowser deployments before 2.63.17 that use public shares. Risk is higher where authenticated users can manage shared directories and where public share URLs are reachable by untrusted parties.
Exploitation context
The sources describe authenticated exploitation requiring a specific path-handling condition. CISA KEV is false in the provided bundle, and no cited source states active exploitation. The issue does not provide integrity or availability impact in the CVSS vector.
Researcher notes
Key condition is inconsistent path normalization during share cleanup. Focus validation on share lifecycle behavior and version verification, not unauthenticated access. Evidence is limited to the vendor advisory, patch reference, CVE data, and VulnCheck advisory.
Mitigation direction
Upgrade filebrowser to 2.63.17 or later.
Review existing public share links and remove stale or unnecessary shares.
Check the GitHub advisory for any additional vendor guidance.
Restrict filebrowser access to trusted authenticated users where feasible.
Validation and detection
Inventory filebrowser deployments and identify versions before 2.63.17.
Confirm upgraded deployments include the vendor patch commit.
Review public share listings for unexpected or dormant shares.
Check logs for unusual share deletion and directory recreation activity, if available.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.