CVE-2026-82237
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.
Scoring
- Severity
- LOW
- CVSS base score
- 3.1
- CVSS vector
- CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- EPSS probability
- 0.17%
- CWE
- CWE-459
- Published
- 2026-08-28
- Last modified
- 2026-08-28
Affected products
- filebrowser filebrowser
Weakness type
Related vulnerabilities
- CVE-2026-87549 — Incomplete cleanup in Downloads in Google Chrome prior to 153.0.8010.36 allowed a remote attacker...
- CVE-2026-87436 — Incomplete cleanup in Browser in Google Chrome prior to 153.0.8010.36 allowed a remote attacker...
- CVE-2026-87446 — Incomplete cleanup in Extensions in Google Chrome prior to 153.0.8010.36 allowed a remote attacker...
- CVE-2026-85043 — Incomplete cleanup in Network in Google Chrome prior to 152.0.7977.82 allowed a remote attacker to...
- CVE-2026-78600 — Incomplete Cleanup in Elastic Cloud on Kubernetes Leading to Unauthorized Cross-Namespace Credential Retention
- CVE-2026-77037 — multer vulnerable to Denial of Service via file descriptor leak on aborted uploads
- CVE-2026-82236 — File Browser 2.63.6 through 2.63.23 Share Link Exposure via File Deletion
- CVE-2026-78947 — Incomplete cleanup in Chromium in Google Chrome prior to 152.0.7977.65 allowed a remote attacker...