How severe is CVE-2017-18916?

CVE-2017-18916 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-18916?

CVE-2017-18916 affects the following packages: 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 CVE-2017-18916?

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

How do I detect CVE-2017-18916 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-18916 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-18916 actively exploited in the wild?

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

CVE-2017-18916 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-18916?

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

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

CVE-2017-18916 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-18916 — mattermost-server

MEDIUMFix: mattermost/mattermost@0968e40

CVE-2017-18916 is a medium-severity (CVSS 5.3) CWE-732 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 Improper Authorization for Integration Requests

Also known asGHSA-x33g-375j-jhf7GO-2026-4467

Published

Jun 19, 2020

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

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

3 pkgs affected

🐹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

An issue was discovered in Mattermost Server before 3.8.2, 3.7.5, and 3.6.7. API endpoint access control does not honor an integration permission restriction.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost-server`	all versions	3.6.7-0.20170420152529-0968e4079e0a`go get github.com/mattermost/mattermost-server@v3.6.7-0.20170420152529-0968e4079e0a`
🐹Go	`github.com/mattermost/mattermost-server`	≥ 3.7.0&&< 3.7.5	3.7.5`go get github.com/mattermost/mattermost-server@v3.7.5`
🐹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.6.7-0.20170420152529-0968e4079e0a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-18916 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 3.8.2, 3.7.5, and 3.6.7. API endpoint access control does not honor an integration permission restriction.

O3 Security · Impact-Aware SCA

Is CVE-2017-18916 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-732CWE-732

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-18916

GHSA-x33g-375j-jhf7

GO-2026-4467

References

Advisorymattermost.com · security updates Advisorynvd.nist.gov · CVE 2017 18916 Webgithub.com · 0968e4079e0aa670254f3fe3a7248d126e3cf877 Webgithub.com · b74e85653660525d351d090a1e1874ae933bcbc8 Webgithub.com · fb325cc339eb8d8efb60dbadc48fd38897201c6f 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-18916 — 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-18916 in your dependencies?