How severe is GHSA-59hf-mpf8-pqjh?

GHSA-59hf-mpf8-pqjh has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-59hf-mpf8-pqjh?

GHSA-59hf-mpf8-pqjh affects the following packages: github.com/mattermost/mattermost/server/v8 (Go). Ecosystems affected: Go.

How do I fix GHSA-59hf-mpf8-pqjh?

Update github.com/mattermost/mattermost/server/v8 to 8.0.0-20240806094731-69a8b3df0f9f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-59hf-mpf8-pqjh is resolved across your whole dependency graph.

How do I detect GHSA-59hf-mpf8-pqjh in my Go dependencies?

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.

How do I mitigate GHSA-59hf-mpf8-pqjh if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-59hf-mpf8-pqjh?

O3 pinpoints whether GHSA-59hf-mpf8-pqjh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-59hf-mpf8-pqjh actively exploited in the wild?

No public exploit code has been indexed for GHSA-59hf-mpf8-pqjh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-59hf-mpf8-pqjh?

GHSA-59hf-mpf8-pqjh has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-59hf-mpf8-pqjh?

GHSA-59hf-mpf8-pqjh is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-59hf-mpf8-pqjh published, and has it been updated?

GHSA-59hf-mpf8-pqjh was published on September 26, 2024 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-59hf-mpf8-pqjh

MEDIUM

Mattermost fails to strip `embeds` from `metadata` when broadcasting `posted` events

Also known asBIT-mattermost-2024-47003CVE-2024-47003GO-2024-3164

Published

Sep 26, 2024

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk43th percentile+0.10%

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

1 pkg affected

🐹github.com/mattermost/mattermost/server/v8

Real-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 does not strip embeds from metadata when broadcasting posted events.

This allows users to include arbitrary embeds in posts, which are then broadcasted via websockets. This can be exploited in many ways, for example to create permalinks with fully customizable content or to trigger a client Side Denial of Service (DoS) by sending a permalink with a non-string message.

The advisory metadata references the appropriate go pseudo version available from pkg.go.dev

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	all versions	8.0.0-20240806094731-69a8b3df0f9f

Detection & mitigation playbook

Open-source dependency

Detect
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.0.0-20240806094731-69a8b3df0f9f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-59hf-mpf8-pqjh 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-59hf-mpf8-pqjh 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-59hf-mpf8-pqjh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Mattermost does not strip `embeds` from `metadata` when broadcasting `posted` events. This allows users to include arbitrary embeds in posts, which are then broadcasted via websockets. This can be exploited in many ways, for example to create permalinks with fully customizable content or to trigger a client Side Denial of Service (DoS) by sending a permalink with a non-string message. The advisory metadata references the appropriate go pseudo version available from pkg.go.dev

O3 Security · Impact-Aware SCA

Is GHSA-59hf-mpf8-pqjh in your dependencies?

O3 detects GHSA-59hf-mpf8-pqjh across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works