How severe is GHSA-m2ch-x2q7-2284?

No CVSS score has been assigned to GHSA-m2ch-x2q7-2284 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m2ch-x2q7-2284?

GHSA-m2ch-x2q7-2284 affects the following packages: github.com/mattermost/mattermost-server (Go). Ecosystems affected: Go.

How do I fix GHSA-m2ch-x2q7-2284?

Update github.com/mattermost/mattermost-server to 3.7.4-0.20170404171331-0b5c0794fdcb or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m2ch-x2q7-2284 is resolved across your whole dependency graph.

How do I detect GHSA-m2ch-x2q7-2284 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m2ch-x2q7-2284 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.

How does O3 Security protect against GHSA-m2ch-x2q7-2284?

O3 pinpoints whether GHSA-m2ch-x2q7-2284 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m2ch-x2q7-2284 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m2ch-x2q7-2284 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 type of vulnerability is GHSA-m2ch-x2q7-2284?

GHSA-m2ch-x2q7-2284 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-m2ch-x2q7-2284 published, and has it been updated?

GHSA-m2ch-x2q7-2284 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

GHSA-m2ch-x2q7-2284

GHSA-m2ch-x2q7-2284 is a Path Traversal vulnerability in github.com/mattermost/mattermost-server. O3 Security confirms whether GHSA-m2ch-x2q7-2284 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Mattermost Server allows an attacker to specify a full pathname of a log file

Also known asCVE-2017-18912GO-2026-4487

Published

May 24, 2022

Updated

Feb 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹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.7.5. It allows an attacker to specify a full pathname of a log file.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost-server`	all versions	3.7.4-0.20170404171331-0b5c0794fdcb

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/mattermost/mattermost-server to 3.7.4-0.20170404171331-0b5c0794fdcb or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m2ch-x2q7-2284 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.
How O3 protects you
O3 pinpoints whether GHSA-m2ch-x2q7-2284 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m2ch-x2q7-2284. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in Mattermost Server before 3.7.5. It allows an attacker to specify a full pathname of a log file.

O3 Security · Impact-Aware SCA

Is GHSA-m2ch-x2q7-2284 in your dependencies?

O3 detects GHSA-m2ch-x2q7-2284 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works