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.
CVE-2026-82237
LOWPre-NVD 3.13.1—Trending — 4 sources updated this weekElevated
EchelonGraph scoreHIGH confidence
Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-08-28. a secondary CVSS source baseline 3.1; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.1Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.1
- EG Score
- 3.1(high)
- EG Risk
- 30(Track)EG Risk 30/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity31% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 6%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
References (3)
- disclosure@vulncheckhttps://github.com/filebrowser/filebrowser/security/advisories/GHSA-m8v4-4w34-rrvf
- disclosure@vulncheckhttps://www.vulncheck.com/advisories/filebrowser-through-2.63.23-stale-share-link-via-file-rename
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/filebrowser/filebrowser/security/advisories/GHSA-m8v4-4w34-rrvf
Vendor Advisories for CVE-2026-82237(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 16:36 UTCEG score recompute
- 2026-08-28 16:36 UTCGHSA enrichment
- 2026-08-28 15:38 UTCEG score recompute
- 2026-08-28 15:38 UTCGHSA enrichment
- 2026-08-28 12:23 UTCEG score recompute
- 2026-08-28 11:23 UTCEG score recompute
- 2026-08-28 11:19 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-82237?
CVE-2026-82237 is a low vulnerability published on August 28, 2026. 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…
When was CVE-2026-82237 disclosed?
CVE-2026-82237 was first published in the National Vulnerability Database on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82237 actively exploited?
CVE-2026-82237 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.7% of all scored CVEs.
What is the CVSS score of CVE-2026-82237?
CVE-2026-82237 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-82237?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82237, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82237
Is Your Infrastructure Affected by CVE-2026-82237?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.