Mattermost Server exposes OAuth personal access tokens to attackers

published 2020-06-19 6y ago modified 2026-06-17 4mo ago also GHSA-876j-jfqf-m7j7 , GO-2025-4197 , EUVD-2017-9974

cvss: 8.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits: 0; none known

An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. It allows attackers to gain privileges by using a registered OAuth application with personal access tokens.

Patch / fix

fixed in 2 distros 2

go github.com/mattermost/mattermost-server 4.1.2, 4.1.2+incompatible, 4.2.1, 4.2.1+incompatible, 4.3.0, 4.3.0+incompatible
mattermost mattermost_server 4.1.2, 4.2.1

suse opensuse

govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20251209T172047-150000.1.127.1

suse advisories SUSE-SU-2025:4395-1

govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2017-18884 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD	2.0	5.5	AV:N/AC:L/Au:S/C:P/I:P/A:N

Affected packages

ecosystem	package	affected	fixed in
go	github.com/mattermost/mattermost-server	<4.1.2 >=4.2.0-rc1, <4.2.1 >=4.3.0-rc1, <4.3.0 <4.1.2+incompatible >=4.2.0-rc1+incompatible, <4.2.1+incompatible >=4.3.0-rc1+incompatible, <4.3.0+incompatible	4.1.2 4.2.1 4.3.0 4.1.2+incompatible 4.2.1+incompatible 4.3.0+incompatible

Classification

Weakness

CWE-269 Improper Privilege Management
CWE-863 Incorrect Authorization

References

mattermost.com /security-updates/
vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2017-18884
advisory
mattermost.com /security-updates
web
github.com /advisories/GHSA-876j-jfqf-m7j7
advisory

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.