CVE-2026-82238

LOWPre-NVD 3.13.1
EchelonGraph scoreMEDIUM confidence

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

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: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
3.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 3.1Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists filebrowser versions 2.24.0 up to and including 2.63.23 as affected. No release containing a fix is confirmed on record.

filebrowser from version 2.24.0 contains a race condition in the TUS upload handler that allows authenticated users to write past the declared Upload-Length by sending concurrent PATCH requests. Attackers can send multiple simultaneous PATCH requests at the same offset to bypass length validation, resulting in files that exceed their declared size and triggering completion hooks for oversized uploads.

CVSS v3
3.1
EG Score
3.1LOWmedium confidence
EG Risk
30
EG Risk 30/100

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 computed (value × EchelonGraph’s weight)
Severity31% × 45%
The EG Score, 3.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (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.

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

August 28, 2026

Last Modified

September 30, 2026

References (2)

Vendor Advisories for CVE-2026-82238(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 13× in last 7d / 54× 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.

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 85 are merged into the row they repeat.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-12 14:55 UTCEG score recompute
  4. 2026-10-11 19:20 UTCEG score recompute
  5. 2026-10-11 16:36 UTCEG score recompute
  6. 2026-10-11 13:54 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-09 06:53 UTCEG score recompute
  11. 2026-10-09 06:52 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-06 11:10 UTCEG score recompute
  16. 2026-10-06 11:10 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-03 14:21 UTCEG score recompute
  21. 2026-10-03 14:21 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  22. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-09-30 18:42 UTCEG score recompute
  25. 2026-09-30 18:42 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
Show 56 more
  1. 2026-09-30 17:38 UTCEG score recompute
  2. 2026-09-30 17:38 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  3. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-09-30 11:52 UTCEG score recompute
  5. 2026-09-30 11:52 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  6. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-09-27 16:14 UTCEG score recompute
  8. 2026-09-27 16:13 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  9. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-09-24 20:35 UTCEG score recompute
  12. 2026-09-24 20:35 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  13. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-09-23 12:08 UTCEG score recompute
  16. 2026-09-23 12:08 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  17. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-09-20 16:29 UTCEG score recompute
  21. 2026-09-20 16:29 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  22. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-09-17 20:51 UTCEG score recompute
  24. 2026-09-17 20:51 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-09-14 21:53 UTCEG score recompute
  29. 2026-09-14 21:53 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  30. 2026-09-12 02:12 UTCEG score recompute
  31. 2026-09-12 02:12 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  32. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  33. 2026-09-09 06:33 UTCEG score recompute
  34. 2026-09-09 06:33 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  35. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  37. 2026-09-06 10:53 UTCEG score recompute
  38. 2026-09-06 10:53 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  39. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  41. 2026-09-03 15:15 UTCEG score recompute
  42. 2026-09-03 15:15 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  43. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  44. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  45. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  46. 2026-08-31 19:32 UTCEG score recompute
  47. 2026-08-31 19:32 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  48. 2026-08-31 18:57 UTCEG score recompute
  49. 2026-08-31 18:57 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  50. 2026-08-31 08:02 UTCEG score recompute
  51. 2026-08-31 08:02 UTCGHSA enrichmentGHSA-6fr9-pm38-mc2g · GitHub severity LOW · GitHub CVSS 3.1
  52. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  53. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  54. 2026-08-28 12:23 UTCEG score recompute
  55. 2026-08-28 11:23 UTCEG score recomputeFirst assessed: 3.1 LOW
  56. 2026-08-28 11:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82238?
CVE-2026-82238 is a low-severity vulnerability; its CVE record was published on August 28, 2026. filebrowser from version 2.24.0 contains a race condition in the TUS upload handler that allows authenticated users to write past the declared Upload-Length by sending concurrent PATCH requests. Attackers can send multiple simultaneous PATCH requests at the same offset to bypass length validation,…
When was CVE-2026-82238 made public?
CVE-2026-82238 was made public on August 14, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 28, 2026. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-82238 actively exploited?
CVE-2026-82238 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82238?
CVE-2026-82238 has a CVSS base score of 3.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82238?
No fix for CVE-2026-82238 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists filebrowser versions 2.24.0 up to and including 2.63.23 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-82238 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82238

Explore →

Is Your Infrastructure Affected by CVE-2026-82238?

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

Book a Demo →Browse All CVEs