How severe is GHSA-cgjg-p2m2-qm4p?

GHSA-cgjg-p2m2-qm4p has a CVSS score of 3.8/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-cgjg-p2m2-qm4p?

GHSA-cgjg-p2m2-qm4p affects the following packages: github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost-server (Go), 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-cgjg-p2m2-qm4p?

Update github.com/mattermost/mattermost/server/v8 to 8.0.0-20251215190648-6404ab29acc0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cgjg-p2m2-qm4p is resolved across your whole dependency graph.

How do I detect GHSA-cgjg-p2m2-qm4p 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-cgjg-p2m2-qm4p 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-cgjg-p2m2-qm4p?

O3 pinpoints whether GHSA-cgjg-p2m2-qm4p 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-cgjg-p2m2-qm4p actively exploited in the wild?

No public exploit code has been indexed for GHSA-cgjg-p2m2-qm4p 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-cgjg-p2m2-qm4p?

GHSA-cgjg-p2m2-qm4p has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 5th 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-cgjg-p2m2-qm4p?

GHSA-cgjg-p2m2-qm4p is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cgjg-p2m2-qm4p published, and has it been updated?

GHSA-cgjg-p2m2-qm4p was published on February 16, 2026 and was last updated on April 1, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-cgjg-p2m2-qm4p: v8 (Low 3.8)

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk5th percentile+0.13%

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

5 pkgs affected

🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost-server🐹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

Mattermost versions 10.11.x <= 10.11.9 fail to enforce invite permissions when updating team settings, which allows team administrators without proper permissions to bypass restrictions and add users to their team via API requests. Mattermost Advisory ID: MMSA-2025-00561

Affected Packages

5 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	all versions	8.0.0-20251215190648-6404ab29acc0
🐹Go	`github.com/mattermost/mattermost-server`	≥ 11.1.0	No fix
🐹Go	`github.com/mattermost/mattermost-server`	≥ 10.11.0	No fix
🐹Go	`github.com/mattermost/mattermost-server`	≥ 11.2.0	No fix
🐹Go	`github.com/mattermost/mattermost-server`	all versions	5.3.2-0.20251215190648-6404ab29acc0

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

Frequently Asked Questions

Mattermost versions 10.11.x <= 10.11.9 fail to enforce invite permissions when updating team settings, which allows team administrators without proper permissions to bypass restrictions and add users to their team via API requests. Mattermost Advisory ID: MMSA-2025-00561

O3 Security · Impact-Aware SCA

Is GHSA-cgjg-p2m2-qm4p in your dependencies?

O3 detects GHSA-cgjg-p2m2-qm4p 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

GHSA-cgjg-p2m2-qm4p