Mattermost Incorrect Authorization vulnerability
Published 30 Jun 2025 · Updated 28 Jul 2025
Is your project on an affected github.com/mattermost/mattermost-server?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <0.0.0-20250513065225-4ae5d647fb88
- Fixed in
- 0.0.0-20250513065225-4ae5d647fb88
go get github.com/mattermost/mattermost-server@v0.0.0-20250513065225-4ae5d647fb88- Affected
- <8.0.0-20250513065225-4ae5d647fb88
- Fixed in
- 8.0.0-20250513065225-4ae5d647fb88
go get github.com/mattermost/mattermost/server/v8@v8.0.0-20250513065225-4ae5d647fb88- Affected
- >=9.11.0 <9.11.16
- Fixed in
- 9.11.16
go get github.com/mattermost/mattermost/server/v8@v9.11.16- Affected
- >=10.5.0 <10.5.6
- Fixed in
- 10.5.6
go get github.com/mattermost/mattermost/server/v8@v10.5.6- Affected
- >=10.6.0 <10.6.6
- Fixed in
- 10.6.6
go get github.com/mattermost/mattermost/server/v8@v10.6.6- Affected
- >=10.7.0 <10.7.3
- Fixed in
- 10.7.3
go get github.com/mattermost/mattermost/server/v8@v10.7.3- Affected
- >=10.8.0 <10.8.1
- Fixed in
- 10.8.1
go get github.com/mattermost/mattermost/server/v8@v10.8.1Details
Mattermost versions 10.5.x <= 10.5.5, 9.11.x <= 9.11.15, 10.8.x <= 10.8.0, 10.7.x <= 10.7.2, 10.6.x <= 10.6.5 fail to properly enforce channel member management permissions when adding participants to playbook runs. This allows authenticated users with member-level permissions to bypass system admin restrictions and add or remove users to/from private channels via the playbook run participants feature, even when the 'Manage Members' permission has been explicitly removed. This can lead to unauthorized access to sensitive channel content and allow guest users to gain channel management privileges.
Is GHSA-v8fr-vxmw-6mf6 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/mattermost/mattermost-server, and gives you the command that fixes it.
More advisories for github.com/mattermost/mattermost-server
- LowCVE-2026-8823Mattermost has an Incorrect Authorization issue in github.com/mattermost/mattermost-server · 1 Oct 2026
- LowCVE-2026-5139Mattermost doesn't enforce administrator authorization on the {{setDefaultInstance}} call within the {{/gitlab connect}} command handler in github.com/mattermost/mattermost-server · 28 Sept 2026
- LowCVE-2026-8074Mattermost doesn't enforce bot-specific permission checks on the user active status endpoint in github.com/mattermost/mattermost-server · 28 Sept 2026
- LowCVE-2026-9162Mattermost doesn't invalidate cached authentication state for active WebSocket connections during global session revocation in github.com/mattermost/mattermost-server · 28 Sept 2026
- LowCVE-2026-6673Mattermost doesn't authenticate Atlassian Connect installed callbacks, allowing a remote unauthenticated attacker to inject a rogue sharedSecret in github.com/mattermost/mattermost-server · 28 Sept 2026
- LowCVE-2026-6062Mattermost doesn't validate channel ownership of an existing subscription before applying edits in github.com/mattermost/mattermost-server · 28 Sept 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.