← Search results
CVE-LINKED INVENTORY35 SECURITY RECORDS
M-Files Corporation"
M-Files Server
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-0931 | 5 Aug 2026 | < 26.5.16015.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-0983 | 18 May 2026 | < 26.5.16015.0; LTS 25.8.15085.13 < LTS 25.8.15085.24; LTS 26.2.15718.8 < LTS 26.2.15718.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-0932 | 1 Apr 2026 | < 26.3.15818.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-0663 | 21 Jan 2026 | < 26.1.15632.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-13008 | 19 Dec 2025 | M-Files Server: < 25.12.15491.7 | M-Files Server: 25.8.15085.18, 25.2.14524.14, 24.8.13981.17 | Update reference ↗ |
| CVE-2025-14267 | 19 Dec 2025 | < 25.12.15491.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-14318 | 18 Dec 2025 | < 25.12.15491.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-11681 | 17 Nov 2025 | M-Files Server: < 25.11.15392.1 | M-Files Server: 25.2.14524.13, 25.8.15085.17 | Update reference ↗ |
| CVE-2025-5964 | 15 Jun 2025 | < 25.6.14925.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-3086 | 4 Apr 2025 | < 25.3.14549 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-0635 | 23 Jan 2025 | < 25.1.14445.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-0619 | 23 Jan 2025 | < 25.1.14445.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-0648 | 23 Jan 2025 | < 25.1.14445.5 | 24.8.13981.14 | Update reference ↗ |
| CVE-2024-10126 | 20 Nov 2024 | < 24.11 | 23.8 SR7; 24.2 SR3; 24.8 SR1 | Update reference ↗ |
| CVE-2024-10127 | 20 Nov 2024 | < 24.11 | < 24.8 LTS SR2 | Update reference ↗ |
| CVE-2024-6789 | 27 Aug 2024 | < 24.8.13981.0; LTS 24.2.0 < LTS 24.2.13421.15 SR2; LTS 23.8.0 < LTS 23.8.12892.0 SR6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-4056 | 26 Apr 2024 | 23.11 < 24.4.13592.4 | 24.2 LTS | Update reference ↗ |
| CVE-2024-0563 | 23 Feb 2024 | < 24.2 | 23.2 SR7; 23.8 SR5 | Update reference ↗ |
| CVE-2023-6910 | 20 Dec 2023 | < 23.12.13195.0 | 23.8 LTS SR4; 23.2 LTS SR6 | Update reference ↗ |
| CVE-2023-6912 | 20 Dec 2023 | < 23.12.13205.0 | 23.2 LTS SR6; 23.8 LTS SR4 | Update reference ↗ |
| CVE-2023-6239 | 28 Nov 2023 | 23.9; 23.10; 23.11 < 23.11.13168.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-6189 | 22 Nov 2023 | < 23.11.13156.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-6117 | 22 Nov 2023 | < 23.11.13156.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-3425 | 25 Aug 2023 | < 23.8.12892.6 | 23.2.12340.14 | Update reference ↗ |
| CVE-2023-3405 | 27 Jun 2023 | < 23.6.12695.3 | 23.2.12340.11 | Update reference ↗ |
| CVE-2023-0384 | 20 Apr 2023 | < 23.4.12528.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-0383 | 20 Apr 2023 | < 23.4.12528.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-0382 | 5 Apr 2023 | < 23.4.12528.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-4858 | 30 Dec 2022 | < 22.10.11846.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-1911 | 30 Nov 2022 | < 22.6.11534.1; < 22.6.11505.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-1606 | 30 Nov 2022 | < 22.3.11164.0; < 22.3.11237.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-41810 | 2 May 2022 | M-Files Server < 22.2.11051.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-41808 | 18 Jan 2022 | Online < 21.11.10775.0; 2018 < 21.11.10775.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-41807 | 18 Jan 2022 | Online < 21.12.10873.0; 2018 < 21.12.10873.0; Classic < 21.12.10873.0; vNext < 21.12.10873.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-41809 | 18 Jan 2022 | Online < 22.1.11017.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.