Uncapped mention keys in user notification properties allow CPU exhaustion during post processing
Mattermost
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Mattermost Mattermost |
|
|
Mattermost
| Product | Affected | Fixed in |
|---|---|---|
| Mattermost Mattermost |
|
|
Mattermost versions 11.10.x <= 11.10.0, 11.9.x <= 11.9.1, 11.8.x <= 11.8.5, 11.7.x <= 11.7.10 fail to cap the number and size of mention keys stored in a user's notification properties, and to bound the quadratic multibyte-keyword matching performed for each post, which allows an authenticated user to degrade post-processing latency and consume excessive CPU on behalf of other members of any channel they share via storing an oversized notify_props.mention_keys list on their own profile.. Mattermost Advisory ID: MMSA-2026-00773
From the CVE record · Mattermost
Mattermost does not limit the number or size of mention keys in a user's notification properties or bound the work needed to match them against posts. An authenticated user can store an oversized mention-key list on their profile, increasing post-processing latency and CPU use for other members of channels they share.
Operators of Mattermost 11.10.x through 11.10.0, 11.9.x through 11.9.1, 11.8.x through 11.8.5, or 11.7.x through 11.7.10 should check their deployments.