Bypass of System Admin User Deactivation Controls for Personal Access Tokens in Mattermost Server
Mattermost
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost/server/v8 Go |
|
|
Mattermost
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost/server/v8 Go |
|
|
10.5.49.11.138.0.0-20250402193107-65343f84a783| github.com/mattermost/mattermost-server Go |
|
|
| github.com/mattermost/mattermost-server/v5 Go |
| No fix yet |
| github.com/mattermost/mattermost-server/v6 Go |
| No fix yet |
Mattermost versions 10.7.x <= 10.7.0, 10.6.x <= 10.6.2, 10.5.x <= 10.5.3, 9.11.x <= 9.11.12 fails to properly invalidate personal access tokens upon user deactivation, allowing deactivated users to maintain full system access by exploiting access token validation flaws via continued usage of previously issued tokens.
From the CVE record · Mattermost
Affected Mattermost versions do not properly invalidate personal access tokens when a user is deactivated. A deactivated user can retain full system access by continuing to use a previously issued token.
Teams running Mattermost 10.7.x through 10.7.0, 10.6.x through 10.6.2, 10.5.x through 10.5.3, or 9.11.x through 9.11.12, or using the listed affected Go packages, should check their deployments.