GHSA-32h7-7j94-8fc2
MEDIUMGHSA-32h7-7j94-8fc2 is a medium-severity (CVSS 4.3) Uncontrolled Resource Consumption vulnerability in github.com/mattermost/mattermost/server/v8. O3 Security confirms whether GHSA-32h7-7j94-8fc2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Mattermost vulnerable to denial of service via large number of emoji reactions
Blast Radius
github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8Real-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 check if a custom emoji reaction exists when sending it to a post and to limit the amount of custom emojis allowed to be added in a post, allowing an attacker sending a huge amount of non-existent custom emojis in a post to crash the mobile app of a user seeing the post. Fetching posts with huge amounts of reactions results in Uncontrolled Resource Consumption.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost/server/v8 | all versions | 8.1.8 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 9.2.0&&< 9.2.4 | 9.2.4 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 9.1.0&&< 9.1.5 | 9.1.5 |
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/v8. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/mattermost/mattermost/server/v8 to 8.1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-32h7-7j94-8fc2 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 pinpoints whether GHSA-32h7-7j94-8fc2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-32h7-7j94-8fc2. 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-32h7-7j94-8fc2 in your dependencies?
O3 detects GHSA-32h7-7j94-8fc2 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.