CVE-2026-0931

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:m-files corporation, epss
Trending — 3 sources updated this week
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

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

Denial-of-service vulnerability in M-Files Server versions before 26.5.16015.3 allows an authenticated admin user to cause the M-Files Server process to crash and fail to restart.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

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
Severity69% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

M-Files Empower

https://empower.m-files.com/security-advisories/CVE-2026-0931

Vendor Advisories for CVE-2026-0931(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 18× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 12:40 UTCEG score recompute
  3. 2026-08-20 12:40 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 14:13 UTCGHSA enrichment
  6. 2026-08-18 15:46 UTCEG score recompute
  7. 2026-08-18 15:46 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 16:42 UTCEG score recompute
  10. 2026-08-17 16:42 UTCGHSA enrichment
  11. 2026-08-16 18:15 UTCEG score recompute
  12. 2026-08-16 18:15 UTCGHSA enrichment
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 19:48 UTCEG score recompute
  16. 2026-08-15 19:48 UTCGHSA enrichment
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 21:21 UTCGHSA enrichment
  19. 2026-08-13 22:53 UTCEG score recompute
  20. 2026-08-13 22:53 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 00:26 UTCEG score recompute
  23. 2026-08-13 00:26 UTCGHSA enrichment
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-12 01:59 UTCEG score recompute
Show 24 more
  1. 2026-08-12 01:59 UTCGHSA enrichment
  2. 2026-08-11 13:42 UTCEPSS rescore
  3. 2026-08-11 03:31 UTCEG score recompute
  4. 2026-08-11 03:31 UTCGHSA enrichment
  5. 2026-08-10 23:59 UTCEPSS rescore
  6. 2026-08-10 05:04 UTCEG score recompute
  7. 2026-08-10 05:04 UTCGHSA enrichment
  8. 2026-08-09 13:46 UTCEPSS rescore
  9. 2026-08-09 06:37 UTCEG score recompute
  10. 2026-08-09 06:37 UTCGHSA enrichment
  11. 2026-08-08 16:37 UTCEPSS rescore
  12. 2026-08-08 08:10 UTCEG score recompute
  13. 2026-08-08 08:10 UTCGHSA enrichment
  14. 2026-08-07 09:43 UTCEG score recompute
  15. 2026-08-07 09:43 UTCGHSA enrichment
  16. 2026-08-06 13:46 UTCEPSS rescore
  17. 2026-08-06 11:56 UTCGHSA enrichment
  18. 2026-08-05 13:29 UTCEG score recompute
  19. 2026-08-05 13:29 UTCGHSA enrichment
  20. 2026-08-05 13:10 UTCEG score recompute
  21. 2026-08-05 13:09 UTCGHSA enrichment
  22. 2026-08-05 10:23 UTCEG score recompute
  23. 2026-08-05 10:11 UTCEG score recompute
  24. 2026-08-05 10:11 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-0931?
CVE-2026-0931 is a medium vulnerability published on August 5, 2026. Denial-of-service vulnerability in M-Files Server versions before 26.5.16015.3 allows an authenticated admin user to cause the M-Files Server process to crash and fail to restart.
When was CVE-2026-0931 disclosed?
CVE-2026-0931 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0931 actively exploited?
CVE-2026-0931 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.4% of all scored CVEs.
What is the CVSS score of CVE-2026-0931?
CVE-2026-0931 has a CVSS v4.0 base score of 6.9 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-0931?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0931, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-0931?

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

Start Free Scan →Browse All CVEs