CVE-2026-32759

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 1.9% (80th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-13408 (ENISA EUVD) · GHSA-ffx7-75gc-jg7c (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.9%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. In versions on the 2.x branch prior to 2.33.8, the TUS resumable upload handler parses the Upload-Length header as a signed 64-bit integer without validating that the value is non-negative, allowing an authenticated user to supply a negative value that instantly satisfies the upload completion condition upon the first PATCH request. This causes the server to fire after_upload exec hooks with empty or partial files, enabling an attacker to repeatedly trigger any configured hook with arbitrary filenames and zero bytes written. The impact ranges from DoS through expensive processing hooks, to command injection amplification when combined with malicious filenames, to abuse of upload-driven workflows like S3 ingestion or database inserts. Even without exec hooks enabled, the negative Upload-Length creates inconsistent cache entries where files are marked complete but contain no data. All deployments using the TUS upload endpoint (/api/tus) are affected, with the enableExec flag escalating the impact from cache inconsistency to remote command execution. 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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.9%
EPSS %ILE
80th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 16, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Jun 10, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

TUS Negative Upload-Length Fires Post-Upload Hooks Prematurely · Advisory · filebrowser/filebrowser · GitHub

https://github.com/filebrowser/filebrowser/security/advisories/GHSA-ffx7-75gc-jg7c
Web page

Fix: Command Execution/Runner/Hooks Features · Issue #5199 · filebrowser/filebrowser · GitHub

https://github.com/filebrowser/filebrowser/issues/5199

Vendor Advisories for CVE-2026-32759(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/filebrowser/filebrowser/v2 @ 2.33.8 (fixes < 2.33.8)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/filebrowser/filebrowser—
  • every version on: no fix on record
—
github.com/filebrowser/filebrowser/v2—
  • every version up to 2.33.8: fixed in 2.33.8
  • every version on: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 185 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 89 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:44 UTCEPSS rescoreEPSS 1.9% · 80th percentile
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 1.9% · 80th percentile
  3. 2026-11-01 07:54 UTCGHSA enrichmentGHSA-ffx7-75gc-jg7c · GitHub severity MODERATE
  4. 2026-11-01 05:57 UTCEG score recompute
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 1.9% · 80th percentile
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 1.9% · 80th percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.9% · 80th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  12. 2026-10-25 14:35 UTCEG score recompute
  13. 2026-10-24 22:53 UTCEG score recompute
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  21. 2026-10-18 03:47 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  23. 2026-10-17 15:49 UTCEG score recompute
  24. 2026-10-16 16:41 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 2.2% · 81st percentile
Show 71 more
  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  4. 2026-10-12 16:14 UTCEG score recompute
  5. 2026-10-11 19:56 UTCEG score recompute
  6. 2026-10-11 17:09 UTCEG score recompute
  7. 2026-10-11 14:36 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  9. 2026-10-11 09:44 UTCOSV refresh
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  17. 2026-10-03 14:25 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  23. 2026-09-26 00:26 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  24. 2026-09-21 22:15 UTCOSV refresh
  25. 2026-09-20 20:15 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  26. 2026-09-18 19:28 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  27. 2026-09-17 19:30 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  28. 2026-09-16 14:08 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  29. 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  30. 2026-09-12 15:01 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  31. 2026-09-11 14:52 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  32. 2026-09-10 09:34 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  33. 2026-09-08 22:00 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  34. 2026-09-07 16:01 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  35. 2026-09-06 13:47 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  36. 2026-09-04 05:06 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  37. 2026-09-02 18:08 UTCOSV refresh
  38. 2026-09-02 14:11 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  39. 2026-09-01 13:53 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  40. 2026-09-01 04:39 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  41. 2026-08-30 19:17 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  42. 2026-08-30 01:22 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  43. 2026-08-28 21:41 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  44. 2026-08-27 14:25 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  45. 2026-08-26 14:46 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  46. 2026-08-25 13:49 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  47. 2026-08-24 14:17 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  48. 2026-08-23 00:19 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  49. 2026-08-21 23:49 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  50. 2026-08-20 22:55 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  51. 2026-08-19 17:03 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  52. 2026-08-18 13:48 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  53. 2026-08-17 13:47 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  54. 2026-08-16 14:56 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  55. 2026-08-16 11:23 UTCEG score recompute
  56. 2026-08-16 02:14 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  57. 2026-08-15 01:30 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  58. 2026-08-14 07:29 UTCEG score recompute
  59. 2026-08-13 22:00 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  60. 2026-08-12 22:16 UTCEG score recompute
  61. 2026-08-12 13:50 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  62. 2026-08-11 21:34 UTCEG score recompute
  63. 2026-08-11 04:42 UTCEG score recompute
  64. 2026-08-11 00:00 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  65. 2026-08-09 18:30 UTCEG score recompute
  66. 2026-08-09 13:46 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  67. 2026-08-09 07:05 UTCEG score recompute
  68. 2026-08-08 16:37 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  69. 2026-08-07 17:42 UTCEG score recompute
  70. 2026-08-06 19:34 UTCEG score recompute
  71. 2026-08-06 13:46 UTCEPSS rescoreEPSS 1.9% · 77th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-32759?
CVE-2026-32759 is a high-severity vulnerability; its CVE record was published on March 16, 2026. File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. In versions on the 2.x branch prior to 2.33.8, the TUS resumable upload handler parses the Upload-Length header as a signed 64-bit integer without validating that…
When was the CVE record for CVE-2026-32759 published?
The CVE record for CVE-2026-32759 was published on March 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-32759 actively exploited?
CVE-2026-32759 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% probability of exploitation in the next 30 days (80th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32759?
CVE-2026-32759 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-32759?
A fix for CVE-2026-32759 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-32759 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32759

Explore →

Is Your Infrastructure Affected by CVE-2026-32759?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs