CVE-2025-12421 is a critical-severity (CVSS 9.9) CWE-303 vulnerability in github.com/mattermost/mattermost/server/v8. A fix is available for github.com/mattermost/mattermost/server/v8 — see the affected versions and patch details below.
Account Takeover via Code Exchange Endpoint
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-12421.
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/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-acda1fb5dd46go get github.com/mattermost/mattermost/server/v8@v8.0.0-20251022210333-acda1fb5dd46 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 11.0.0&&< 11.0.3 | 11.0.3go get github.com/mattermost/mattermost-server@v11.0.3 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 10.12.0&&< 10.12.2 | 10.12.2go get github.com/mattermost/mattermost-server@v10.12.2 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 10.11.0&&< 10.11.5 | 10.11.5go get github.com/mattermost/mattermost-server@v10.11.5 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 10.5.0&&< 10.5.13 | 10.5.13go get github.com/mattermost/mattermost-server@v10.5.13 |
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/v8, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2025-12421 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.
Frequently Asked Questions
Is CVE-2025-12421 in your dependencies?
Find it across Go, including transitive dependencies.