Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY457 SECURITY RECORDS

Mattermost

Mattermost

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This CVE identity is linked to the Lifecycle record Mattermost. Use that record for publisher support phases and retirement dates.

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2025-20630 16 Jan 2025 ≤ <=2.22.0 2.23.0 Update reference ↗
CVE-2025-20621 16 Jan 2025 10.2.0 ≤ 10.2.0; 9.11.0 ≤ 9.11.5; 10.0.0 ≤ 10.0.3; 10.1.0 ≤ 10.1.3 10.3.0; 2.23.0; 10.2.1; 9.11.6; 10.0.4; 10.1.4 Update reference ↗
CVE-2025-20072 16 Jan 2025 ≤ 2.22.0 2.23.0 Update reference ↗
CVE-2025-0476 15 Jan 2025 ≤ 2.22.0 2.23.0 Update reference ↗
CVE-2025-20088 15 Jan 2025 10.2.0; 9.11.0 ≤ 9.11.5; 10.0.0 ≤ 10.0.3; 10.1.0 ≤ 10.1.3 10.3.0; 10.2.1; 9.11.6; 10.0.4; 10.1.4 Update reference ↗
CVE-2025-20086 15 Jan 2025 10.2.0; 9.11.0 ≤ 9.11.5; 10.0.0 ≤ 10.0.3; 10.1.0 ≤ 10.1.3 10.3.0; 10.2.1; 9.11.6; 10.0.4; 10.1.4 Update reference ↗
CVE-2025-21083 15 Jan 2025 ≤ 2.22.0 2.23.0 Update reference ↗
CVE-2025-20036 15 Jan 2025 ≤ 2.22.0 2.23.0 Update reference ↗
CVE-2025-21088 15 Jan 2025 10.2.0; 9.11.0 ≤ 9.11.5; 10.0.0 ≤ 10.0.3; 10.1.0 ≤ 10.1.3 10.3.0; 10.2.1; 9.11.6; 10.0.4; 10.1.4 Update reference ↗
CVE-2025-22445 9 Jan 2025 10.0.* ≤ 10.2.* 10.3.0 Update reference ↗
CVE-2025-20033 9 Jan 2025 10.2.0; 9.11.0 ≤ 9.11.5; 10.0.0 ≤ 10.0.3; 10.1.0 ≤ 10.1.3 10.3.0; 10.2.1; 9.11.6; 10.0.4; 10.1.4 Update reference ↗
CVE-2025-22449 9 Jan 2025 9.11.0 ≤ 9.11.5 10.3.0; 9.11.6 Update reference ↗
CVE-2024-11358 16 Dec 2024 ≤ 2.21.0 2.22.0 Update reference ↗
CVE-2024-54682 16 Dec 2024 10.1.0 ≤ 10.1.2; 10.0.0 ≤ 10.0.2; 9.11.0 ≤ 9.11.4; 9.5.0 ≤ 9.5.12 10.2.0; 10.1.3; 10.0.3; 9.11.5; 9.5.13 Update reference ↗
CVE-2024-54083 16 Dec 2024 10.1.0 ≤ 10.1.2; 10.0.0 ≤ 10.0.2; 9.11.0 ≤ 9.11.4; 9.5.0 ≤ 9.5.12 10.2.0; 2.22.0; 10.1.3; 10.0.3; 9.11.5; 9.5.13 Update reference ↗
CVE-2024-48872 16 Dec 2024 10.1.0 ≤ 10.1.2; 10.0.0 ≤ 10.0.2; 9.11.0 ≤ 9.11.4; 9.5.0 ≤ 9.5.12 10.2.0; 10.1.3; 10.0.3; 9.11.5; 9.5.13 Update reference ↗
CVE-2024-12247 5 Dec 2024 9.7.0 ≤ 9.7.5; 9.8.0 ≤ 9.8.2; 9.9.0 ≤ 9.9.2 10.0.0; 9.7.6; 9.8.3; 9.9.3 Update reference ↗
CVE-2024-11599 28 Nov 2024 10.0.0 ≤ 10.0.1; 10.1.0 ≤ 10.1.1; 9.11.0 ≤ 9.11.3; 9.5.0 ≤ 9.5.11 10.2.0; 10.0.2; 10.1.2; 9.11.4; 9.5.12 Update reference ↗
CVE-2024-52032 9 Nov 2024 10.0.0; 9.11.0 ≤ 9.11.2 10.1.0; 10.0.1; 9.11.3 Update reference ↗
CVE-2024-36250 9 Nov 2024 9.11.0 ≤ 9.11.2; 9.5.0 ≤ 9.5.10 10.1.0; 9.11.3; 9.5.11 Update reference ↗
CVE-2024-42000 9 Nov 2024 9.10.0 ≤ 9.10.2; 9.11.0 ≤ 9.11.1; 9.5.0 ≤ 9.5.9; 10.0.0 10.1.0; 9.10.3; 9.11.2; 9.5.10; 10.0.1 Update reference ↗
CVE-2024-46872 29 Oct 2024 9.10.0 ≤ 9.10.2; 9.11.0 ≤ 9.11.1; 9.5.0 ≤ 9.5.9 10.0.0; 9.10.3; 9.11.2; 9.5.10 Update reference ↗
CVE-2024-47401 29 Oct 2024 9.10.0 ≤ 9.10.2; 9.11.0 ≤ 9.11.1; 9.5.0 ≤ 9.5.9 10.0.0; 9.10.3; 9.11.2; 9.5.10 Update reference ↗
CVE-2024-50052 29 Oct 2024 9.10.0 ≤ 9.10.2; 9.11.0 ≤ 9.11.1; 9.5.0 ≤ 9.5.9 10.0.0; 9.10.3; 9.11.2; 9.5.10 Update reference ↗
CVE-2024-10241 29 Oct 2024 9.5.0 ≤ 9.5.9 9.8.0; 9.5.10 Update reference ↗
CVE-2024-10214 28 Oct 2024 9.11.0 ≤ 9.11.1; 9.5.0 ≤ 9.5.9 10.0.0; 9.11.2; 9.5.10 Update reference ↗
CVE-2024-9155 26 Sep 2024 9.10.0 ≤ 9.10.1; 9.9.0 ≤ 9.9.2; 9.5.0 ≤ 9.5.8 9.11.0; 9.10.2; 9.9.3; 9.5.9 Update reference ↗
CVE-2024-47003 26 Sep 2024 9.11.0; 9.5.0 ≤ 9.5.8 10.0.0; 9.11.1; 9.5.9 Update reference ↗
CVE-2024-42406 26 Sep 2024 9.11.0; 9.10.0 ≤ 9.10.1; 9.9.0 ≤ 9.9.2; 9.5.0 ≤ 9.5.8 10.0.0; 9.11.1; 9.10.2; 9.9.3; 9.5.9 Update reference ↗
CVE-2024-45843 26 Sep 2024 9.5.0 ≤ 9.5.8 9.11.0; 9.5.9 Update reference ↗
CVE-2024-47145 26 Sep 2024 9.5.0 ≤ 9.5.8 9.11.0; 9.5.9 Update reference ↗
CVE-2024-45835 16 Sep 2024 ≤ 5.8.0 5.9.0 Update reference ↗
CVE-2024-39772 16 Sep 2024 ≤ 5.8.0 5.9.0 Update reference ↗
CVE-2024-45833 16 Sep 2024 ≤ 2.18.0 2.19.0 Update reference ↗
CVE-2024-39613 16 Sep 2024 ≤ 5.8.0 5.9.0 Update reference ↗
CVE-2024-43105 23 Aug 2024 ≤ 1.0.0 1.0.1 Update reference ↗
CVE-2024-43780 22 Aug 2024 9.9.0 ≤ 9.9.1; 9.5.0 ≤ 9.5.7; 9.10.0; 9.8.0 ≤ 9.8.2 9.11.0; 9.9.2; 9.5.8; 9.10.1; 9.8.3 Update reference ↗
CVE-2024-42497 22 Aug 2024 9.9.0 ≤ 9.9.1; 9.5.0 ≤ 9.5.7; 9.10.0; 9.8.0 ≤ 9.8.2 9.11.0; 9.9.2; 9.5.8; 9.10.1; 9.8.3 Update reference ↗
CVE-2024-40884 22 Aug 2024 9.5.0 ≤ 9.5.7; 9.10.0 9.11.0; 9.5.8; 9.10.1 Update reference ↗
CVE-2024-8071 22 Aug 2024 9.9.0 ≤ 9.9.1; 9.5.0 ≤ 9.5.7; 9.10.0; 9.8.0 ≤ 9.8.2 9.11.0; 9.9.2; 9.5.8; 9.10.1; 9.8.3 Update reference ↗
CVE-2024-42411 22 Aug 2024 9.9.0 ≤ 9.9.1; 9.5.0 ≤ 9.5.7; 9.10.0; 9.8.0 ≤ 9.8.2 9.11.0; 9.9.2; 9.5.8; 9.10.1; 9.8.3 Update reference ↗
CVE-2024-40886 22 Aug 2024 9.9.0 ≤ 9.9.1; 9.5.0 ≤ 9.5.7; 9.10.0; 9.8.0 ≤ 9.8.2 9.11.0; 9.9.2; 9.5.8; 9.10.1; 9.8.3 Update reference ↗
CVE-2024-43813 22 Aug 2024 9.5.0 ≤ 9.5.7; 9.10.0 9.11.0; 9.5.8; 9.10.1 Update reference ↗
CVE-2024-39810 22 Aug 2024 9.5.0 ≤ 9.5.7; 9.10.0 9.11.0; 9.5.8; 9.10.1 Update reference ↗
CVE-2024-32939 22 Aug 2024 9.9.0 ≤ 9.9.1; 9.5.0 ≤ 9.5.7; 9.10.0; 9.8.0 ≤ 9.8.2 9.11.0; 9.9.2; 9.5.8; 9.10.1; 9.8.3 Update reference ↗
CVE-2024-39836 22 Aug 2024 9.9.0 ≤ 9.9.1; 9.5.0 ≤ 9.5.7; 9.10.0; 9.8.0 ≤ 9.8.2 9.11.0; 9.9.2; 9.5.8; 9.10.1; 9.8.3 Update reference ↗
CVE-2024-41926 1 Aug 2024 9.9.0; 9.5.0 ≤ 9.5.6 9.10.0; 9.9.1; 9.5.7 Update reference ↗
CVE-2024-41162 1 Aug 2024 9.9.0; 9.5.0 ≤ 9.5.6; 9.7.0 ≤ 9.7.5; 9.8.0 ≤ 9.8.1 9.10.0; 9.9.1; 9.5.7; 9.7.6; 9.8.2 Update reference ↗
CVE-2024-41144 1 Aug 2024 9.9.0; 9.5.0 ≤ 9.5.6; 9.7.0 ≤ 9.7.5; 9.8.0 ≤ 9.8.1 9.10.0; 9.9.1; 9.5.7; 9.7.6; 9.8.2 Update reference ↗
CVE-2024-39839 1 Aug 2024 9.9.0; 9.5.0 ≤ 9.5.6; 9.7.0 ≤ 9.7.5; 9.8.0 ≤ 9.8.1 9.10.0; 9.9.1; 9.5.7; 9.7.6; 9.8.2 Update reference ↗

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.