CVE-2025-6227Published Jul 18, 2025 · Jul 18Updated Oct 28
Invite token is used as part of the secure communication
Mattermost
Low2.2Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost-server Go |
|
|
Mattermost
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost-server Go |
|
|
10.5.8+incompatible| github.com/mattermost/mattermost/server/v8 Go |
|
|
| github.com/mattermost/mattermost-server/v5 Go |
| No fix yet |
| github.com/mattermost/mattermost-server/v6 Go |
| No fix yet |
Mattermost versions 10.5.x <= 10.5.7, 9.11.x <= 9.11.16 fail to negotiate a new token when accepting the invite which allows a user that intercepts both invite and password to send synchronization payloads to the server that originally created the invite via the REST API.
From the CVE record · Mattermost
Affected Mattermost versions fail to negotiate a new token when an invite is accepted. A user who intercepts both the invite and password can send synchronization payloads via the REST API to the server that created the invite.
Operators of Mattermost 10.5.x through 10.5.7 or 9.11.x through 9.11.16, and users of the listed affected Go packages, should check their deployments.