Mattermost password hash disclosure vulnerabilityGHSA-r67m-mf7v-qp7j
MEDIUMFix: mattermost/mattermost#24362GHSA-r67m-mf7v-qp7j is a medium-severity (CVSS 4.9) Information Exposure vulnerability in github.com/mattermost/mattermost-server/v6. A fix is available for github.com/mattermost/mattermost-server/v6 — see the affected versions and patch details below.
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 GHSA-r67m-mf7v-qp7j.
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/v6🐹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/v6🐹github.com/mattermost/mattermost-server/v5🐹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 fails to properly sanitize the user object when updating the username, resulting in the password hash being included in the response body.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost-server/v6 | ≥ 5.4.0-rc1&&< 7.8.12 | 7.8.12go get github.com/mattermost/mattermost-server/v6@v7.8.12 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 8.0.0&&< 8.0.4 | 8.0.4go get github.com/mattermost/mattermost/server/v8@v8.0.4 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 8.1.0&&< 8.1.3 | 8.1.3go get github.com/mattermost/mattermost/server/v8@v8.1.3 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 9.0.0&&< 9.0.1 | 9.0.1go get github.com/mattermost/mattermost/server/v8@v9.0.1 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | all versions | 8.0.0-20230825233148-f787fd63368ago get github.com/mattermost/mattermost/server/v8@v8.0.0-20230825233148-f787fd63368a |
| 🐹Go | github.com/mattermost/mattermost-server/v6 | all versions | 5.3.2-0.20230825233148-f787fd63368ago get github.com/mattermost/mattermost-server/v6@v5.3.2-0.20230825233148-f787fd63368a |
Affected Products
mattermostmattermostDetection & 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/v6, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost-server/v6 to 7.8.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r67m-mf7v-qp7j is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-r67m-mf7v-qp7j in your dependencies?
Find it across Go, including transitive dependencies.