GHSA-mp6x-97xj-9x62 is a critical-severity (CVSS 9.9) CWE-303 vulnerability in github.com/mattermost/mattermost/server/v8. O3 Security confirms whether GHSA-mp6x-97xj-9x62 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Mattermost fails to to verify the token used during code exchange
Real-World Exposure
github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-serverReal-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 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost/server/v8 | all versions | 8.0.0-20251022210333-acda1fb5dd46 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 11.0.0&&< 11.0.3 | 11.0.3 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 10.12.0&&< 10.12.2 | 10.12.2 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 10.11.0&&< 10.11.5 | 10.11.5 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 10.5.0&&< 10.5.13 | 10.5.13 |
Detection & 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/v8. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/mattermost/mattermost/server/v8 to 8.0.0-20251022210333-acda1fb5dd46 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mp6x-97xj-9x62 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mp6x-97xj-9x62 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-mp6x-97xj-9x62. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mp6x-97xj-9x62 in your dependencies?
O3 detects GHSA-mp6x-97xj-9x62 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.