How severe is GHSA-876j-jfqf-m7j7?

No CVSS score has been assigned to GHSA-876j-jfqf-m7j7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-876j-jfqf-m7j7?

GHSA-876j-jfqf-m7j7 affects the following packages: github.com/mattermost/mattermost-server (Go), github.com/mattermost/mattermost-server (Go), github.com/mattermost/mattermost-server (Go). Ecosystems affected: Go.

How do I fix GHSA-876j-jfqf-m7j7?

Update github.com/mattermost/mattermost-server to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-876j-jfqf-m7j7 is resolved across your whole dependency graph.

How do I detect GHSA-876j-jfqf-m7j7 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. 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-876j-jfqf-m7j7 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-876j-jfqf-m7j7?

O3 pinpoints whether GHSA-876j-jfqf-m7j7 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-876j-jfqf-m7j7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-876j-jfqf-m7j7 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-876j-jfqf-m7j7?

GHSA-876j-jfqf-m7j7 is classified as Improper Privilege Management (CWE-269). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-876j-jfqf-m7j7 published, and has it been updated?

GHSA-876j-jfqf-m7j7 was published on May 24, 2022 and was last updated on December 9, 2025. 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-876j-jfqf-m7j7

GHSA-876j-jfqf-m7j7 is a Improper Privilege Management vulnerability in github.com/mattermost/mattermost-server. O3 Security confirms whether GHSA-876j-jfqf-m7j7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Mattermost Server exposes OAuth personal access tokens to attackers

Also known asCVE-2017-18884GO-2025-4197

Published

May 24, 2022

Updated

Dec 9, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server

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

An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. It allows attackers to gain privileges by using a registered OAuth application with personal access tokens.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost-server`	all versions	4.1.2
🐹Go	`github.com/mattermost/mattermost-server`	≥ 4.2.0-rc1&&< 4.2.1	4.2.1
🐹Go	`github.com/mattermost/mattermost-server`	≥ 4.3.0-rc1&&< 4.3.0	4.3.0

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

Frequently Asked Questions

An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. It allows attackers to gain privileges by using a registered OAuth application with personal access tokens.

O3 Security · Impact-Aware SCA

Is GHSA-876j-jfqf-m7j7 in your dependencies?

O3 detects GHSA-876j-jfqf-m7j7 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