Mattermost up to 10.11.6/10.12.2/11.0.4 WebSocket Request Field improper validation of specified type of input
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Mattermost up to 10.11.6/10.12.2/11.0.4. This vulnerability affects unknown code of the component WebSocket Request Field Handler. This manipulation causes improper validation of specified type of input. This vulnerability is handled as CVE-2025-12689. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Mattermost up to 10.11.6/10.12.2/11.0.4. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component WebSocket Request Field Handler. The manipulation with an unknown input leads to a improper validation of specified type of input vulnerability. The CWE definition for the vulnerability is CWE-1287. The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type. As an impact it is known to affect availability. The summary by CVE is:
Mattermost versions 11.0.x <= 11.0.4, 10.12.x <= 10.12.2, 10.11.x <= 10.11.6 fail to check WebSocket request field for proper UTF-8 format, which allows attacker to crash Calls plug-in via sending malformed request.
The advisory is shared at mattermost.com. This vulnerability is known as CVE-2025-12689 since 11/04/2025. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 10.11.7, 10.12.3, 11.0.5 or 11.1.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2025-203918) and CERT Bund (WID-SEC-2025-2880). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Mattermost Mattermost
Product
Type
Name
Version
- 10.11.0
- 10.11.1
- 10.11.2
- 10.11.3
- 10.11.4
- 10.11.5
- 10.11.6
- 10.12.0
- 10.12.1
- 10.12.2
- 11.0.0
- 11.0.1
- 11.0.2
- 11.0.3
- 11.0.4
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (Mattermost): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper validation of specified type of inputCWE: CWE-1287 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Mattermost 10.11.7/10.12.3/11.0.5/11.1.0
Timeline
11/04/2025 CVE reserved12/17/2025 Advisory disclosed
12/17/2025 VulDB entry created
02/27/2026 VulDB entry last update
Sources
Advisory: mattermost.comStatus: Confirmed
CVE: CVE-2025-12689 (🔒)
GCVE (CVE): GCVE-0-2025-12689
GCVE (VulDB): GCVE-100-337021
EUVD: 🔒
CERT Bund: WID-SEC-2025-2880 - Mattermost Server und Desktop: Mehrere Schwachstellen
Entry
Created: 12/17/2025 21:26Updated: 02/27/2026 11:34
Changes: 12/17/2025 21:26 (63), 12/20/2025 20:21 (1), 02/27/2026 11:34 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.