How severe is CVE-2017-18905?

CVE-2017-18905 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-18905?

CVE-2017-18905 affects the following packages: github.com/mattermost/mattermost-server (Go), github.com/mattermost/mattermost-server (Go). Ecosystems affected: Go.

How do I fix CVE-2017-18905?

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

How do I detect CVE-2017-18905 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 CVE-2017-18905 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2017-18905 actively exploited in the wild?

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

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

CVE-2017-18905 is classified as CWE-613 (CWE-613). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-18905 published, and has it been updated?

CVE-2017-18905 was published on June 19, 2020 and was last updated on October 24, 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-2017-18905 — mattermost-server

MEDIUMFix: mattermost/mattermost@15ad24d

CVE-2017-18905 is a medium-severity (CVSS 5.3) CWE-613 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.

Mattermost Server has Insufficient Session Expiration when used as an OAuth 2.0 service provider

Also known asGHSA-g24c-fx4v-xg9wGO-2026-4306

Published

Jun 19, 2020

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

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

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 4.0.0, 3.10.2, and 3.9.2, when used as an OAuth 2.0 service provider, Session invalidation was mishandled.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost-server`	all versions	3.9.2`go get github.com/mattermost/mattermost-server@v3.9.2`
🐹Go	`github.com/mattermost/mattermost-server`	≥ 3.10.0&&< 3.10.2	3.10.2`go get github.com/mattermost/mattermost-server@v3.10.2`

Affected Products

1 product · 2 configurations

Application

mattermost servermattermost

≥ 3.10.0 && < 3.10.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.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-18905 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

An issue was discovered in Mattermost Server before 4.0.0, 3.10.2, and 3.9.2, when used as an OAuth 2.0 service provider, Session invalidation was mishandled.

O3 Security · Impact-Aware SCA

Is CVE-2017-18905 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-613CWE-613

Weaponization

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

OpenSSF Scorecard

Package health score

mattermost

7.3/10

Dependency-Update-Tool10/10

Code-Review10/10

Maintained10/10

Branch-Protection4/10

Vulnerabilities0/10

Assessed Nov 3, 2026

Timeline

Disclosed

Jun 19, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2017-18905

GHSA-g24c-fx4v-xg9w

GO-2026-4306

References

Advisorymattermost.com · security updates Advisorynvd.nist.gov · CVE 2017 18905 Webgithub.com · 15ad24d160cb4604d0605ebbfa53d11a57820706 Webgithub.com · b17fca0d5ee7557e3df1cf1d1da8bd749859e35f Webgithub.com · fbc170733e86f09b46ba754dd03304733d2f482f Webmattermost.com · security updates Packagegithub.com · mattermost

Related vulnerabilities

This CVE is medium severity; 6 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-8823CVE-2026-6046CVE-2026-7387

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2017-18905 — mattermost-server

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-2017-18905 in your dependencies?