How severe is CVE-2022-2401?

CVE-2022-2401 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-2401?

CVE-2022-2401 affects the following packages: github.com/mattermost/mattermost-server/v6 (Go), github.com/mattermost/mattermost-server/v6 (Go), github.com/mattermost/mattermost-server/v6 (Go), github.com/mattermost/mattermost-server/v6 (Go). Ecosystems affected: Go.

How do I fix CVE-2022-2401?

Update github.com/mattermost/mattermost-server/v6 to 6.3.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2401 is resolved across your whole dependency graph.

How do I detect CVE-2022-2401 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/v6, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-2401 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2022-2401 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-2401 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 CVE-2022-2401?

CVE-2022-2401 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 58th 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 CVE-2022-2401?

CVE-2022-2401 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-2401 published, and has it been updated?

CVE-2022-2401 was published on July 14, 2022 and was last updated on October 28, 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

Not in CISA KEV

MEDIUM severity

CVE-2022-2401 — mattermost-server

MEDIUM

CVE-2022-2401 is a medium-severity (CVSS 6.5) Information Exposure vulnerability in github.com/mattermost/mattermost-server/v6. A fix is available for github.com/mattermost/mattermost-server/v6 — see the affected versions and patch details below.

Team members could access sensitive information of other users via an API call

Also known asBIT-mattermost-2022-2401GHSA-7ggc-5r84-xf54GO-2022-0540

Published

Jul 14, 2022

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 3, 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 CVE-2022-2401.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs58th percentile — riskier than 58% 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

4 pkgs affected

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

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

Unrestricted information disclosure of all users in Mattermost version 6.7.0 and earlier allows team members to access some sensitive information by directly accessing the APIs.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost-server/v6`	all versions	6.3.9`go get github.com/mattermost/mattermost-server/v6@v6.3.9`
🐹Go	`github.com/mattermost/mattermost-server/v6`	≥ 6.4.0&&< 6.5.2	6.5.2`go get github.com/mattermost/mattermost-server/v6@v6.5.2`
🐹Go	`github.com/mattermost/mattermost-server/v6`	≥ 6.6.0&&< 6.6.2	6.6.2`go get github.com/mattermost/mattermost-server/v6@v6.6.2`
🐹Go	`github.com/mattermost/mattermost-server/v6`	≥ 6.7.0&&< 6.7.1	6.7.1`go get github.com/mattermost/mattermost-server/v6@v6.7.1`

Affected Products

1 product · 5 configurations

Application

mattermost servermattermost

≥ 6.4.0 && < 6.5.2

3 versions

6.6.06.6.16.7.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/v6, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost-server/v6 to 6.3.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2401 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

Unrestricted information disclosure of all users in Mattermost version 6.7.0 and earlier allows team members to access some sensitive information by directly accessing the APIs.

O3 Security · Impact-Aware SCA

Is CVE-2022-2401 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-200Information Exposure

Weaponization

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

Timeline

Disclosed

Jul 14, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-2401

GHSA-7ggc-5r84-xf54

BIT-mattermost-2022-2401

GO-2022-0540

References

Advisorygithub.com · CVE 2022 2401.json Advisorynvd.nist.gov · CVE 2022 2401 Webmattermost.com · security updates Webmattermost.com · security updates Packagegithub.com · mattermost server

Related vulnerabilities

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

CVE-2025-11776CVE-2025-11777CVE-2025-53971CVE-2025-36530CVE-2025-8402CVE-2025-49222CVE-2025-47870CVE-2025-8023

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-2401 — mattermost-server

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-2401 in your dependencies?