How severe is GHSA-mc2f-jgj6-6cp3?

GHSA-mc2f-jgj6-6cp3 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-mc2f-jgj6-6cp3?

GHSA-mc2f-jgj6-6cp3 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), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go). Ecosystems affected: Go.

How do I fix GHSA-mc2f-jgj6-6cp3?

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

How do I detect GHSA-mc2f-jgj6-6cp3 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-mc2f-jgj6-6cp3 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.

Is GHSA-mc2f-jgj6-6cp3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mc2f-jgj6-6cp3 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-mc2f-jgj6-6cp3?

GHSA-mc2f-jgj6-6cp3 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th 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-mc2f-jgj6-6cp3?

GHSA-mc2f-jgj6-6cp3 is classified as CWE-303 (CWE-303). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mc2f-jgj6-6cp3 published, and has it been updated?

GHSA-mc2f-jgj6-6cp3 was published on May 30, 2025 and was last updated on June 3, 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

Not in CISA KEV

MEDIUM severity

Mattermost fails to properly invalidate personal access tokens upon user deactivationGHSA-mc2f-jgj6-6cp3

MEDIUMFix: mattermost/mattermost@65343f8

GHSA-mc2f-jgj6-6cp3 is a medium-severity (CVSS 5.4) CWE-303 vulnerability in github.com/mattermost/mattermost/server/v8. A fix is available for github.com/mattermost/mattermost/server/v8 — see the affected versions and patch details below.

Also known asCVE-2025-3230GO-2025-3731

Published

May 30, 2025

Updated

Jun 3, 2025

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mc2f-jgj6-6cp3.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs14th percentile — riskier than 14% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹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.7.x <= 10.7.0, 10.6.x <= 10.6.2, 10.5.x <= 10.5.3, 9.11.x <= 9.11.12 fails to properly invalidate personal access tokens upon user deactivation, allowing deactivated users to maintain full system access by exploiting access token validation flaws via continued usage of previously issued tokens.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 10.7.0-rc1&&< 10.7.1	10.7.1`go get github.com/mattermost/mattermost/server/v8@v10.7.1`
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 10.6.0-rc1&&< 10.6.3	10.6.3`go get github.com/mattermost/mattermost/server/v8@v10.6.3`
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 10.0.0-rc1&&< 10.5.4	10.5.4`go get github.com/mattermost/mattermost/server/v8@v10.5.4`
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 9.0.0-rc1&&< 9.11.13	9.11.13`go get github.com/mattermost/mattermost/server/v8@v9.11.13`
🐹Go	`github.com/mattermost/mattermost/server/v8`	all versions	8.0.0-20250402193107-65343f84a783`go get github.com/mattermost/mattermost/server/v8@v8.0.0-20250402193107-65343f84a783`

Affected Products

1 product · 4 configurations

Application

mattermost servermattermost

≥ 10.7.0 && < 10.7.1

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost/server/v8 to 10.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mc2f-jgj6-6cp3 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-mc2f-jgj6-6cp3 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

CWE Classification

CWE-303CWE-303

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 30, 2025

Last updated

Jun 3, 2025

Identifiers

GHSA-mc2f-jgj6-6cp3

GO-2025-3731

References

Advisorynvd.nist.gov · CVE 2025 3230 Webgithub.com · 65343f84a7830fa8078fe3df879fca924e4fac01 Webmattermost.com · security updates Packagegithub.com · mattermost

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs affecting v8 are rated as high or higher (top: high).

CVE-2026-8823CVE-2026-6046CVE-2026-7387CVE-2026-6961CVE-2026-7184CVE-2026-6689CVE-2026-6739CVE-2026-3433

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJun 3, 2025