Persistent notification timing attack causing server denial of service
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 10.11.15+incompatible, 11.4.5+incompatible, 11.5.4+incompatible, 11.6.1+incompatible, 11.6.1, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Mattermost Mattermost
From 11.6.0 · through 11.6.0; From 11.5.0 · through 11.5.3; From 11.4.0 · through 11.4.4; From 10.11.0 · through 10.11.14
- github.com/mattermost/mattermost-serverGo
From 10.11.0+incompatible · fixed in 10.11.15+incompatible; From 11.4.0+incompatible · fixed in 11.4.5+incompatible; From 11.5.0+incompatible · fixed in 11.5.4+incompatible; From 11.6.0+incompatible · fixed in 11.6.1+incompatible
- github.com/mattermost/mattermost-serverGo
From 11.6.0 · fixed in 11.6.1
- github.com/mattermost/mattermost-serverGo
From 11.5.0 · fixed in 11.5.4
- github.com/mattermost/mattermost-serverGo
From 11.4.0 · fixed in 11.4.5
- github.com/mattermost/mattermost-serverGo
From 10.11.0 · fixed in 10.11.15