CVE-2026-82237
LOW
2,3
Source: [email protected]
Attack Vector: network
Attack Complexity: high
Privileges Required: low
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A
LOW
3,1
Source: [email protected]
Attack Vector: network
Attack Complexity: high
Privileges Required: low
User Interaction: none
Scope: unchanged
Confidentiality: low
Integrity: none
Availability: none
Description
AI Translation Available
filebrowser through 2.63.23 does not remove share records when a shared file is renamed (only deletion triggers share cleanup). The share record is keyed by path, so it survives the rename and remains dormant (returning 404 while the path is empty). When any new, unrelated file later appears at the original shared path — via re-upload, another user with create permission, or a hook — the stale public share link serves that new file under the original link's password and expiry settings, unexpectedly exposing it.
459
Incomplete Cleanup
DraftCommon Consequences
Security Scopes Affected:
Other
Confidentiality
Integrity
Potential Impacts:
Other
Read Application Data
Modify Application Data
Dos: Resource Consumption (Other)
Applicable Platforms
All platforms may be affected
https://github.com/filebrowser/filebrowser/security/advisories/GHSA-m8v4-4w34-r…
https://www.vulncheck.com/advisories/filebrowser-through-2.63.23-stale-share-li…