Persistent notification timing attack causing server denial of service
Mattermost
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost-server Go |
|
Mattermost
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost-server Go |
|
≥ 11.6.0+incompatible · < 11.6.1+incompatible
|
Mattermost versions 11.6.x <= 11.6.0, 11.5.x <= 11.5.3, 11.4.x <= 11.4.4, 10.11.x <= 10.11.14 fail to archive the channel before removing persistent notifications which allows authenticated user to crash the server via timing the creation of persistent notification message between the server deleting existing persistent notifications and archiving the channel.. Mattermost Advisory ID: MMSA-2026-00637
From the CVE record · Mattermost
Mattermost can remove persistent notifications before archiving a channel. An authenticated user can crash the server by timing the creation of a persistent notification message between those operations.
Teams running Mattermost 11.6.0, 11.5.0–11.5.3, 11.4.0–11.4.4, or 10.11.0–10.11.14, including the affected Go package variants, should check their deployments.