GHSA-jf5h-xfw4-p8gp
LOWMattermost GitHub Plugin Bot Identity Validation Bypass Allows Arbitrary GitHub Reaction Injection
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.
Blast Radius
github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost🐹github.com/mattermost/mattermost🐹github.com/mattermost/mattermost-plugin-githubReal-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.11.x <= 10.11.6 and Mattermost GitHub plugin versions <=2.4.0 fail to validate plugin bot identity in reaction forwarding which allows attackers to hijack the GitHub reaction feature to make users add reactions to arbitrary GitHub objects via crafted notification posts.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.11.0-rc1&&< 10.11.7-0.20251106103514-3b05384dd014 | 10.11.7-0.20251106103514-3b05384dd014 |
| 🐹Go | github.com/mattermost/mattermost | all versions | 10.11.7-0.20251106103514-3b05384dd014 |
| 🐹Go | github.com/mattermost/mattermost | ≥ 11.0.0-alpha.1&&< 11.1.0 | 11.1.0 |
| 🐹Go | github.com/mattermost/mattermost-plugin-github | all versions | 1.0.1-0.20250829075715-0deffcfc6bee |
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 10.11.7-0.20251106103514-3b05384dd014 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jf5h-xfw4-p8gp 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-jf5h-xfw4-p8gp 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-jf5h-xfw4-p8gp. 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-jf5h-xfw4-p8gp in your dependencies?
O3 detects GHSA-jf5h-xfw4-p8gp across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.