CVE-2026-82235

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

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

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. A secondary CVSS source baseline 5.9; 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 week
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

filebrowser through 2.63.23 fails to validate named pipes in directory archive and public download handlers, allowing attackers to trigger blocking open syscalls. Authenticated users or anonymous visitors with public share links can repeatedly request archives containing named pipes to pin server goroutines and exhaust connection resources.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/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)
Severity59% × 45%
The EG Score, 5.9 of 10.
Exploitation0.5% × 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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

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

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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.

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 24, 2026

Advisory Details (3)

Auto-updated Aug 28, 2026
Fix referenced — no release confirmed yet. Sources: github_commit, github.
Web page

filebrowser through 2.63.23 Denial of Service via named pipes | Advisories | VulnCheck

https://www.vulncheck.com/advisories/filebrowser-through-2.63.23-denial-of-service-via-named-pipes
GitHub commit

commit 586d198d (filebrowser/filebrowser)

Fix landed in filebrowser/filebrowser commit 586d198d — awaiting tagged release

https://github.com/filebrowser/filebrowser/commit/586d198d
GitHub advisoryMentions a patch (unverified)

Archive downloads hang forever on named pipes · Advisory · filebrowser/filebrowser · GitHub

https://github.com/filebrowser/filebrowser/security/advisories/GHSA-8q5j-8wcr-8v2v

Vendor Advisories for CVE-2026-82235(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 17× in last 7d / 79× 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 98 of 126 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 28 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd 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.5% · 42nd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-10-10 03:53 UTCEG score recompute
  10. 2026-10-10 03:53 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-09 02:42 UTCEG score recompute
  13. 2026-10-09 02:42 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-10-08 00:54 UTCEG score recompute
  16. 2026-10-08 00:54 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-10-06 17:15 UTCEG score recompute
  19. 2026-10-06 17:15 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-10-05 16:49 UTCEG score recompute
  23. 2026-10-05 16:49 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  24. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-04 14:44 UTCEG score recompute
Show 73 more
  1. 2026-10-04 14:44 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  2. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-03 14:19 UTCEG score recompute
  4. 2026-10-03 14:19 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  5. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-02 12:50 UTCEG score recompute
  7. 2026-10-02 12:50 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  8. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-01 12:03 UTCEG score recompute
  10. 2026-10-01 12:03 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  11. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-09-30 11:36 UTCEG score recompute
  13. 2026-09-30 11:36 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  14. 2026-09-29 11:10 UTCEG score recompute
  15. 2026-09-29 11:10 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  16. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-09-28 09:52 UTCEG score recompute
  18. 2026-09-28 09:52 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  19. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  20. 2026-09-27 09:27 UTCEG score recompute
  21. 2026-09-27 09:27 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  22. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-09-26 08:44 UTCEG score recompute
  24. 2026-09-26 08:44 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  25. 2026-09-24 20:35 UTCEG score recompute
  26. 2026-09-24 20:35 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  27. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  28. 2026-09-24 08:00 UTCEG score recompute
  29. 2026-09-24 08:00 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  30. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  31. 2026-09-23 07:34 UTCEG score recompute
  32. 2026-09-23 07:34 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  33. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  34. 2026-09-22 07:09 UTCEG score recompute
  35. 2026-09-22 07:09 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  36. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  37. 2026-09-21 06:43 UTCEG score recompute
  38. 2026-09-21 06:43 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  39. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  40. 2026-09-20 06:17 UTCEG score recompute
  41. 2026-09-20 06:17 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  42. 2026-09-19 05:50 UTCEG score recompute
  43. 2026-09-19 05:50 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  44. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  45. 2026-09-18 05:23 UTCEG score recompute
  46. 2026-09-18 05:23 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  47. 2026-09-17 04:58 UTCEG score recompute
  48. 2026-09-17 04:58 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  49. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  50. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  51. 2026-09-16 04:32 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  52. 2026-09-15 03:58 UTCEG score recompute
  53. 2026-09-15 03:58 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  54. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  55. 2026-09-14 03:29 UTCEG score recompute
  56. 2026-09-14 03:29 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  57. 2026-09-13 03:04 UTCEG score recompute
  58. 2026-09-13 03:04 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  59. 2026-09-12 02:38 UTCEG score recompute
  60. 2026-09-12 02:38 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  61. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  62. 2026-09-11 02:12 UTCEG score recompute
  63. 2026-09-11 02:12 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  64. 2026-09-10 01:45 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  65. 2026-09-09 01:19 UTCEG score recompute
  66. 2026-09-09 01:19 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  67. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  68. 2026-09-08 00:53 UTCEG score recompute
  69. 2026-09-08 00:53 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  70. 2026-09-07 00:27 UTCEG score recompute
  71. 2026-09-07 00:27 UTCGHSA enrichmentGHSA-j27f-mghv-p674 · GitHub severity HIGH · GitHub CVSS 5.9
  72. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  73. 2026-09-05 23:56 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82235?
CVE-2026-82235 is a medium-severity vulnerability; its CVE record was published on August 28, 2026. filebrowser through 2.63.23 fails to validate named pipes in directory archive and public download handlers, allowing attackers to trigger blocking open syscalls. Authenticated users or anonymous visitors with public share links can repeatedly request archives containing named pipes to pin server…
When was CVE-2026-82235 made public?
CVE-2026-82235 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 24, 2026; the record at its source may have been updated since.
Is CVE-2026-82235 actively exploited?
CVE-2026-82235 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82235?
CVE-2026-82235 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82235?
A fix for CVE-2026-82235 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-82235 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-82235?

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

Book a Demo →Browse All CVEs