CVE-2025-46702 is a medium-severity (CVSS 5.4) CWE-863 vulnerability in github.com/mattermost/mattermost-server. A fix is available for github.com/mattermost/mattermost-server — see the affected versions and patch details below.
Mattermost Playbooks allows privilege escalation through improper access control in playbook run participant management
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-46702.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost-server | all versions | 0.0.0-20250513065225-4ae5d647fb88go get github.com/mattermost/mattermost-server@v0.0.0-20250513065225-4ae5d647fb88 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | all versions | 8.0.0-20250513065225-4ae5d647fb88go get github.com/mattermost/mattermost/server/v8@v8.0.0-20250513065225-4ae5d647fb88 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 9.11.0&&< 9.11.16 | 9.11.16go get github.com/mattermost/mattermost/server/v8@v9.11.16 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.5.0&&< 10.5.6 | 10.5.6go get github.com/mattermost/mattermost/server/v8@v10.5.6 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.6.0&&< 10.6.6 | 10.6.6go get github.com/mattermost/mattermost/server/v8@v10.6.6 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.7.0&&< 10.7.3 | 10.7.3go get github.com/mattermost/mattermost/server/v8@v10.7.3 |
Affected Products
mattermost servermattermostDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost-server to 0.0.0-20250513065225-4ae5d647fb88 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-46702 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2025-46702 in your dependencies?
Find it across Go, including transitive dependencies.