Insufficient token rotation validation in remote cluster invite confirmation
- 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.14+incompatible, 11.5.2+incompatible, 8.0.0-20260313190740-742e0be95074, 11.5.2, 10.11.14, and 1 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.5.x <= 11.5.1, 10.11.x <= 10.11.13 fail to validate that the RefreshedToken differs from the original invite token during remote cluster invite confirmation which allows an authenticated attacker to bypass token rotation and reuse the original invite token via sending a crafted invite confirmation with a RefreshedToken matching the original token. Mattermost Advisory ID: MMSA-2026-00575
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Mattermost Mattermost
From 11.5.0 · through 11.5.1; From 10.11.0 · through 10.11.13
- github.com/mattermost/mattermost-serverGo
From 10.11.0+incompatible · fixed in 10.11.14+incompatible; From 11.5.0+incompatible · fixed in 11.5.2+incompatible
- github.com/mattermost/mattermost-server/v5Go
All versions
- github.com/mattermost/mattermost-server/v6Go
All versions
- github.com/mattermost/mattermost/server/v8Go
fixed in 8.0.0-20260313190740-742e0be95074
- github.com/mattermost/mattermost/server/v8Go
From 11.5.0 · fixed in 11.5.2
- github.com/mattermost/mattermost/server/v8Go
From 10.11.0 · fixed in 10.11.14
- github.com/mattermost/mattermost-serverGo
fixed in 5.3.2-0.20260313190740-742e0be95074