GHSA-8jhh-3jf2-pfwr — mattermost-server
MEDIUMGHSA-8jhh-3jf2-pfwr is a medium-severity (CVSS 6.5) Information Exposure vulnerability in github.com/mattermost/mattermost-server. A fix is available for github.com/mattermost/mattermost-server — see the affected versions and patch details below.
Mattermost vulnerable to information disclosure
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-8jhh-3jf2-pfwr.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-8jhh-3jf2-pfwr plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server/v5🐹github.com/mattermost/mattermost-server/v6Real-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
When running in a High Availability configuration, Mattermost fails to sanitize some of the user_updated and post_deleted events broadcast to all users, leading to disclosure of sensitive information to some of the users with currently connected Websocket clients.
Issue Identifier: MMSA-2023-00138
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 3.3.0&&< 7.1.6 | 7.1.6go get github.com/mattermost/mattermost-server@v7.1.6 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 7.7.0&&< 7.7.2 | 7.7.2go get github.com/mattermost/mattermost-server@v7.7.2 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 7.1.0&&< 7.1.6 | 7.1.6go get github.com/mattermost/mattermost-server@v7.1.6 |
| 🐹Go | github.com/mattermost/mattermost-server/v5 | ≥ 5.0.0&&< 7.1.6 | 7.1.6go get github.com/mattermost/mattermost-server/v5@v7.1.6 |
| 🐹Go | github.com/mattermost/mattermost-server/v6 | ≥ 6.0.0&&< 7.1.6 | 7.1.6go get github.com/mattermost/mattermost-server/v6@v7.1.6 |
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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost-server to 7.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8jhh-3jf2-pfwr 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8jhh-3jf2-pfwr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8jhh-3jf2-pfwr. 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-8jhh-3jf2-pfwr in your dependencies?
O3 Security finds GHSA-8jhh-3jf2-pfwr across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.