filebrowser through 2.63.23 Stale Share Link via File Rename (CVE-2026-82237) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-82237

filebrowser through 2.63.23 Stale Share Link via File Rename

Answer in brief

CVE-2026-82237 records a Unknown severity vulnerability in filebrowser through 2.63.23 Stale Share Link via File Rename. The current sources do not mark it as known exploited. The current feed maps filebrowser/filebrowser (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 28, 2026Updated Aug 28, 2026Source checked Aug 28, 2026First seen by HOL Aug 28, 2026Material review Aug 28, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps filebrowser/filebrowser (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
filebrowser/filebrowsergeneric	0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for filebrowser/filebrowser.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 28, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.