Mattermost doesn't prevent disclosure of created user passwordGHSA-wvgv-4fc3-2rcp
MEDIUMFix: mattermost/mattermost@3057ae7GHSA-wvgv-4fc3-2rcp is a medium-severity (CVSS 6.5) CWE-522 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-wvgv-4fc3-2rcp.
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/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹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.5.x <= 11.5.1, 10.11.x <= 10.11.13, 11.4.x <= 11.4.3 doesn't prevent disclosure of created user password which allows a malicious attacker to impersonate a user via the use of some of those passwords.. Mattermost Advisory ID: MMSA-2026-00614
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 11.5.0&&< 11.5.2 | 11.5.2go get github.com/mattermost/mattermost/server/v8@v11.5.2 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.11.0&&< 10.11.14 | 10.11.14go get github.com/mattermost/mattermost/server/v8@v10.11.14 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 11.4.0&&< 11.4.4 | 11.4.4go get github.com/mattermost/mattermost/server/v8@v11.4.4 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | all versions | 8.0.0-20260311102650-3057ae7e83e9go get github.com/mattermost/mattermost/server/v8@v8.0.0-20260311102650-3057ae7e83e9 |
| 🐹Go | github.com/mattermost/mattermost-server | all versions | 5.3.2-0.20260311102650-3057ae7e83e9go get github.com/mattermost/mattermost-server@v5.3.2-0.20260311102650-3057ae7e83e9 |
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 11.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wvgv-4fc3-2rcp 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-wvgv-4fc3-2rcp in your dependencies?
Find it across Go, including transitive dependencies.