CVE-2025-52904

HIGHPre-NVD 8.08.0
EchelonGraph scoreMEDIUM confidence

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

Score 8.0 from GitHub Security Advisory (severity: HIGH) published 2025-06-30. A secondary CVSS source baseline 8.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2025-19557 (ENISA EUVD) · GHSA-hc8f-m8g5-8362 (GitHub Security Advisories) · GO-2025-3793 (OSV.dev)Source: ENISA EUVD

8.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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: 1.1%CVSS: 8.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. In versions of the web application on the 2.x branch, all users have a scope assigned, and they only have access to the files within that scope. The Command Execution feature of Filebrowser allows the execution of shell commands which are not restricted to the scope, potentially giving an attacker read and write access to all files managed by the server. Until this issue is fixed, the maintainers recommend to completely disable Execute commands for all accounts. Since the command execution is an inherently dangerous feature that is not used by all deployments, it should be possible to completely disable it in the application's configuration. 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.0
EG Score
8.0HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity80% × 45%
Impact severity (EG Severity): CVSS 8.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
66th
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.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is its impact severity (EG Severity), not escalated.

EG Severity
8.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-06). 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 low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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 low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

June 26, 2025

Last Modified

June 9, 2026

Advisory Details (6)

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

Command Execution not Limited to Scope · Advisory · filebrowser/filebrowser · GitHub

https://github.com/filebrowser/filebrowser/security/advisories/GHSA-hc8f-m8g5-8362
Web page

Sandboxing Applications with Bubblewrap: Securing a Basic Shell | sloonz's blog

https://sloonz.github.io/posts/sandboxing-1
Web page

GO-2025-3793 - Go Packages

https://pkg.go.dev/vuln/GO-2025-3793
Web pageMentions a patch (unverified)

advisories/2025/SBA-ADV-20250326-01_Filebrowser_Command_Execution_Not_Limited_To_Scope at public · sbaresearch/advisories · GitHub

https://github.com/sbaresearch/advisories/tree/public/2025/SBA-ADV-20250326-01_Filebrowser_Command_Execution_Not_Limited_To_Scope
Web page

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

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

GitHub - GoogleContainerTools/distroless: 🥑 Language focused docker images, minus the operating system. · GitHub

https://github.com/GoogleContainerTools/distroless

Vendor Advisories for CVE-2025-52904(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(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 217 rows on record for this CVE, as 96 entries (4 repeats merged).

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 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  2. 2026-11-12 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  3. 2026-11-11 16:36 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  4. 2026-11-10 16:40 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  5. 2026-11-09 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  6. 2026-11-08 16:37 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  7. 2026-11-07 16:37 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  8. 2026-11-07 15:06 UTCEchelonGraph re-scored
  9. 2026-11-07 15:06 UTCGHSA enrichmentGHSA-hc8f-m8g5-8362 · GitHub severity HIGH · GitHub CVSS 8.0
  10. 2026-11-06 16:34 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  11. 2026-11-05 16:35 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  12. 2026-11-04 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  13. 2026-11-03 16:45 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  14. 2026-11-02 16:43 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  15. 2026-11-01 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  16. 2026-10-31 22:48 UTCEchelonGraph re-scored
  17. 2026-10-31 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  18. 2026-10-30 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  19. 2026-10-29 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  20. 2026-10-28 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  21. 2026-10-27 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  22. 2026-10-26 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  23. 2026-10-25 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  24. 2026-10-25 16:19 UTCEchelonGraph re-scored
  25. 2026-10-25 06:30 UTCEchelonGraph re-scored
Show 71 more
  1. 2026-10-24 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-10-23 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  3. 2026-10-22 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  4. 2026-10-21 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-10-20 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  6. 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  7. 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  8. 2026-10-18 05:27 UTCEchelonGraph re-scored
  9. 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  10. 2026-10-16 16:39 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  11. 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  12. 2026-10-14 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  13. 2026-10-13 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  14. 2026-10-12 16:58 UTCEchelonGraph re-scored
  15. 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  16. 2026-10-11 20:32 UTCEchelonGraph re-scored
  17. 2026-10-11 18:43 UTCEchelonGraph re-scored
  18. 2026-10-11 15:19 UTCEchelonGraph re-scored
  19. 2026-10-11 13:47 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  20. 2026-10-10 19:59 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  21. 2026-10-09 20:06 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  22. 2026-10-08 17:10 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  23. 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  24. 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  25. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  26. 2026-10-04 23:21 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  27. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  28. 2026-10-02 10:41 UTCOSV refresh
  29. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  30. 2026-09-30 15:02 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  31. 2026-09-28 13:50 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  32. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  33. 2026-09-26 00:25 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  34. 2026-09-24 14:02 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  35. 2026-09-23 13:47 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  36. 2026-09-21 21:06 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  37. 2026-09-20 20:15 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  38. 2026-09-19 15:42 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  39. 2026-09-18 19:27 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  40. 2026-09-17 19:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  41. 2026-09-16 14:07 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  42. 2026-09-16 05:14 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  43. 2026-09-13 16:46 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  44. 2026-09-13 08:54 UTCOSV refresh
  45. 2026-09-12 15:00 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  46. 2026-09-11 14:52 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  47. 2026-09-11 09:36 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  48. 2026-09-10 09:34 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  49. 2026-09-08 21:59 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  50. 2026-09-07 16:00 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  51. 2026-09-06 13:47 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  52. 2026-09-05 15:28 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  53. 2026-09-04 05:06 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  54. 2026-09-02 14:11 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  55. 2026-09-01 13:53 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  56. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  57. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  58. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  59. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  60. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  61. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  62. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  63. 2026-08-25 09:41 UTCOSV refresh
  64. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  65. 2026-08-24 09:22 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  66. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  67. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  68. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  69. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  70. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  71. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.9% · 56th percentile

Frequently asked(5)

What is CVE-2025-52904?
CVE-2025-52904 is a high-severity vulnerability; its CVE record was published on June 26, 2025. File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. In versions of the web application on the 2.x branch, all users have a scope assigned, and they only have access to the files within that scope. The…
When was the CVE record for CVE-2025-52904 published?
The CVE record for CVE-2025-52904 was published on June 26, 2025. 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 9, 2026; the record at its source may have been updated since.
Is CVE-2025-52904 actively exploited?
CVE-2025-52904 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-52904?
CVE-2025-52904 has a CVSS base score of 8.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-52904?
A fix for CVE-2025-52904 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-52904 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-2025-52904

Explore →

Is Your Infrastructure Affected by CVE-2025-52904?

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