CVE-2026-82237filebrowser through 2.63.23 Stale Share Link via File Rename
Updated under an hour ago ()
Does this affect you?
It affects filebrowser. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 3.1 LOW (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
- Weakness (CWE)
- CWE-459
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- VulnCheck
- NVD analysis
- Awaiting Analysis
- Record last updated
- Aug 28, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
filebrowser filebrowser filebrowser:filebrowser (from the name) | through 2.63.23 | CNA record |
References
- https://github.com/filebrowser/filebrowser/security/advisories/GHSA-m8v4-4w34-rrvfvendor-advisory
- https://www.vulncheck.com/advisories/filebrowser-through-2.63.23-stale-share-link-via-file-renamethird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.