How severe is GHSA-ffpr-pfr4-g354?

GHSA-ffpr-pfr4-g354 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-ffpr-pfr4-g354?

GHSA-ffpr-pfr4-g354 affects the following packages: 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-ffpr-pfr4-g354?

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

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

How do I mitigate GHSA-ffpr-pfr4-g354 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 GHSA-ffpr-pfr4-g354 actively exploited in the wild?

No public exploit code has been indexed for GHSA-ffpr-pfr4-g354 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-ffpr-pfr4-g354?

GHSA-ffpr-pfr4-g354 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th 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-ffpr-pfr4-g354?

GHSA-ffpr-pfr4-g354 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 GHSA-ffpr-pfr4-g354 published, and has it been updated?

GHSA-ffpr-pfr4-g354 was published on May 26, 2026 and was last updated on July 7, 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

Mattermost doesn't sanitize team member data when returned via API to users without elevated permissionsGHSA-ffpr-pfr4-g354

MEDIUM

GHSA-ffpr-pfr4-g354 is a medium-severity (CVSS 4.3) Information Exposure vulnerability in github.com/mattermost/mattermost-server. A fix is available for github.com/mattermost/mattermost-server — see the affected versions and patch details below.

Also known asCVE-2026-3636GO-2026-5818

Published

May 26, 2026

Updated

Jul 7, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 7, 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-ffpr-pfr4-g354.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-ffpr-pfr4-g354 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected

🐹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 11.6.x <= 11.6.0, 11.5.x <= 11.5.3, 11.4.x <= 11.4.4, 10.11.x <= 10.11.14 fail to sanitize team member data when returned via API to users without elevated permissions which allows a user without permissions to get data about team members roles via invoking various team API endpoints. Mattermost Advisory ID: MMSA-2026-00626.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost-server`	≥ 11.6.0&&< 11.6.1	11.6.1`go get github.com/mattermost/mattermost-server@v11.6.1`
🐹Go	`github.com/mattermost/mattermost-server`	≥ 11.5.0&&< 11.5.4	11.5.4`go get github.com/mattermost/mattermost-server@v11.5.4`
🐹Go	`github.com/mattermost/mattermost-server`	≥ 11.4.0&&< 11.4.5	11.4.5`go get github.com/mattermost/mattermost-server@v11.4.5`
🐹Go	`github.com/mattermost/mattermost-server`	≥ 10.11.0&&< 10.11.15	10.11.15`go get github.com/mattermost/mattermost-server@v10.11.15`

Affected Products

1 product · 4 configurations

Application

mattermost servermattermost

≥ 11.6.0 && < 11.6.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost-server to 11.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ffpr-pfr4-g354 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

O3 Security · Impact-Aware SCA

Is GHSA-ffpr-pfr4-g354 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-200Information Exposure

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

May 26, 2026

Last updated

Jul 7, 2026

Identifiers

GHSA-ffpr-pfr4-g354

GO-2026-5818

References

Advisorynvd.nist.gov Webmattermost.com Packagegithub.com

Related vulnerabilities

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

CVE-2026-5139CVE-2026-8074CVE-2026-9162CVE-2026-6673CVE-2026-6062CVE-2026-6046CVE-2026-7387CVE-2026-6961

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 7, 2026

Mattermost doesn't sanitize team member data when returned via API to users without elevated permissionsGHSA-ffpr-pfr4-g354

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 GHSA-ffpr-pfr4-g354 in your dependencies?