How severe is GHSA-wwhj-pw6h-f8hw?

GHSA-wwhj-pw6h-f8hw has a CVSS score of 3.1/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-wwhj-pw6h-f8hw?

GHSA-wwhj-pw6h-f8hw affects the following packages: github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go). Ecosystems affected: Go.

How do I fix GHSA-wwhj-pw6h-f8hw?

Update github.com/mattermost/mattermost/server/v8 to 10.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wwhj-pw6h-f8hw is resolved across your whole dependency graph.

How do I detect GHSA-wwhj-pw6h-f8hw 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-wwhj-pw6h-f8hw 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-wwhj-pw6h-f8hw?

O3 pinpoints whether GHSA-wwhj-pw6h-f8hw 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-wwhj-pw6h-f8hw actively exploited in the wild?

No public exploit code has been indexed for GHSA-wwhj-pw6h-f8hw 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 type of vulnerability is GHSA-wwhj-pw6h-f8hw?

GHSA-wwhj-pw6h-f8hw is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-wwhj-pw6h-f8hw published, and has it been updated?

GHSA-wwhj-pw6h-f8hw was published on April 14, 2025 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-wwhj-pw6h-f8hw

LOWFix: mattermost/mattermost@68c11e9

GHSA-wwhj-pw6h-f8hw is a low-severity (CVSS 3.1) CWE-863 vulnerability in github.com/mattermost/mattermost/server/v8. O3 Security confirms whether GHSA-wwhj-pw6h-f8hw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Mattermost Incorrect Authorization vulnerability

Also known asCVE-2025-2424GO-2025-3611

Published

Apr 14, 2025

Updated

Feb 4, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Real-World Exposure

3 pkgs affected

🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹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 versions 10.5.x <= 10.5.1, 9.11.x <= 9.11.9 fail to check if a file has been deleted when creating a bookmark which allows an attacker who knows the IDs of deleted files to obtain metadata of the files via bookmark creation.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 10.5.0&&< 10.5.2	10.5.2
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 9.11.0&&< 9.11.10	9.11.10
🐹Go	`github.com/mattermost/mattermost/server/v8`	all versions	8.0.0-20250213231113-68c11e9ecb71

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 10.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wwhj-pw6h-f8hw 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-wwhj-pw6h-f8hw 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-wwhj-pw6h-f8hw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-wwhj-pw6h-f8hw in your dependencies?

O3 detects GHSA-wwhj-pw6h-f8hw 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