How severe is GHSA-jxc4-w54c-qv5r?

No CVSS score has been assigned to GHSA-jxc4-w54c-qv5r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jxc4-w54c-qv5r?

GHSA-jxc4-w54c-qv5r affects the following packages: github.com/mattermost/mattermost-server (Go), github.com/mattermost/mattermost-server (Go). Ecosystems affected: Go.

How do I fix GHSA-jxc4-w54c-qv5r?

Update github.com/mattermost/mattermost-server to 3.7.5-0.20170421192444-247cd1e51a8c or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jxc4-w54c-qv5r is resolved across your whole dependency graph.

How do I detect GHSA-jxc4-w54c-qv5r 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-jxc4-w54c-qv5r 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-jxc4-w54c-qv5r actively exploited in the wild?

No public exploit code has been indexed for GHSA-jxc4-w54c-qv5r 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-jxc4-w54c-qv5r?

GHSA-jxc4-w54c-qv5r has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 54th 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-jxc4-w54c-qv5r?

GHSA-jxc4-w54c-qv5r is classified as CWE-916 (CWE-916). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jxc4-w54c-qv5r published, and has it been updated?

GHSA-jxc4-w54c-qv5r was published on May 24, 2022 and was last updated on February 19, 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

Mattermost Server uses weak hashing for OAuth, email verification tokens and invitationsGHSA-jxc4-w54c-qv5r

Fix: mattermost/mattermost@247cd1e

GHSA-jxc4-w54c-qv5r is a CWE-916 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-2017-18917GO-2026-4463

Published

May 24, 2022

Updated

Feb 19, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐹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 3.8.2, 3.7.5, and 3.6.7. Weak hashing was used for e-mail invitations, OAuth, and e-mail verification tokens.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost-server`	all versions	3.7.5-0.20170421192444-247cd1e51a8c`go get github.com/mattermost/mattermost-server@v3.7.5-0.20170421192444-247cd1e51a8c`
🐹Go	`github.com/mattermost/mattermost-server`	≥ 3.8.0&&< 3.8.2	3.8.2`go get github.com/mattermost/mattermost-server@v3.8.2`

Affected Products

1 product · 3 configurations

Application

mattermost servermattermost

≥ 3.8.0 && < 3.8.2

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 3.7.5-0.20170421192444-247cd1e51a8c or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jxc4-w54c-qv5r 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

An issue was discovered in Mattermost Server before 3.8.2 and 3.7.5. Weak hashing was used for e-mail invitations, OAuth, and e-mail verification tokens.