Skip to main content
VulnerabilityPublished

CVE-2026-72838: FileBrowser versions before 2.63.19 fail to enforce the declared Upload-Length in the TUS resumable-upload PATCH endpoint, allowing authenticated

Affects filebrowserSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.63.19 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.63.19
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade filebrowser/filebrowser to 2.63.19.

Affected software

ProductAffectedFixed in
GitHubfilebrowser/filebrowserpkg:github/filebrowser/filebrowserOther threatsAffected
  • <2.63.19
Fixed in
  • 2.63.19

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict authenticated user permissions to trusted users only and monitor disk usage to mitigate potential denial of service from disk exhaustion.

Description

FileBrowser versions prior to 2.63.19 contain a vulnerability in the TUS resumable-upload PATCH endpoint where the declared Upload-Length is not enforced. This allows authenticated users to send oversized request bodies, writing arbitrary data to disk beyond the declared length. The consequence is potential exhaustion of disk space, leading to service unavailability.

References

Community reviews

Loading reviews…