Mattermost fails to properly validate OAuth state tokens during OpenID Connect authenticationGHSA-3x39-62h4-f8j6
CRITICALFix: mattermost/mattermost#34296GHSA-3x39-62h4-f8j6 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.
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 GHSA-3x39-62h4-f8j6.
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 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12, 11.0.x <= 11.0.3 fail to properly validate OAuth state tokens during OpenID Connect authentication which allows an authenticated attacker with team creation privileges to take over a user account via manipulation of authentication data during the OAuth completion flow. This requires email verification to be disabled (default: disabled), OAuth/OpenID Connect to be enabled, and the attacker to control two users in the SSO system with one of them never having logged into Mattermost.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost/server/v8 | all versions | 8.0.0-20251028000919-d3ed703dc833go get github.com/mattermost/mattermost/server/v8@v8.0.0-20251028000919-d3ed703dc833 |
| 🐹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 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 11.0.0&&< 11.0.4 | 11.0.4go get github.com/mattermost/mattermost-server@v11.0.4 |
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-20251028000919-d3ed703dc833 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3x39-62h4-f8j6 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 GHSA-3x39-62h4-f8j6 in your dependencies?
Find it across Go, including transitive dependencies.