← Back to results
Vulnerability record · public intelligence
CVE-2026-32759
HIGH

File Browser TUS Negative Upload-Length Fires Post-Upload Hooks Prematurely

Published Mar 19, 2026 · Updated Oct 23, 2026 · Also known as GHSA-ffx7-75gc-jg7c, GO-2026-4713

Severity · CVSSHIGH · 8.1
Known exploitationNot listed
EPSS / likelihood2.25%
QFinch risk score10 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

File Browser TUS Negative Upload-Length Fires Post-Upload Hooks Prematurely

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

> [!NOTE] > **This feature has been disabled by default for all installations from v2.33.8 onwards, including for existent installations**. To exploit this vulnerability, the instance administrator must turn on a feature and ignore all the warnings about known vulnerabilities. We're publishing this new advisory to make it clear that all vulnerabilities concerning this feature are disclosed. > > For more information about tracking vulnerability issues related to the Command Execution features, check https://github.com/filebrowser/filebrowser/issues/5199.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
MEDIUM
Confidence
10%
Aliases
GHSA-ffx7-75gc-jg7c, GO-2026-4713

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Source repository ↗

Record history

Published Mar 19, 2026 · Last refreshed Oct 23, 2026