How severe is CVE-2025-9079?

CVE-2025-9079 has a CVSS score of 8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-9079?

CVE-2025-9079 affects the following packages: github.com/mattermost/mattermost-server (Go), github.com/mattermost/mattermost-server (Go), github.com/mattermost/mattermost-server (Go), github.com/mattermost/mattermost-server (Go), github.com/mattermost/mattermost-server (Go), github.com/mattermost/mattermost/server/v8 (Go). Ecosystems affected: Go.

How do I fix CVE-2025-9079?

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

How do I detect CVE-2025-9079 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 CVE-2025-9079 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 CVE-2025-9079?

O3 pinpoints whether CVE-2025-9079 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 CVE-2025-9079 actively exploited in the wild?

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

CVE-2025-9079 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 CVE-2025-9079 published, and has it been updated?

CVE-2025-9079 was published on September 19, 2025 and was last updated on July 31, 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

CVE-2025-9079

HIGH

CVE-2025-9079 is a high-severity (CVSS 8) Path Traversal vulnerability in github.com/mattermost/mattermost-server. O3 Security confirms whether CVE-2025-9079 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Admin RCE via prepackaged plugins by way of misconfigured imports directory

Also known asGHSA-qx3f-6vq3-8j8mGO-2025-3977

Published

Sep 19, 2025

Updated

Jul 31, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Blast Radius

6 pkgs affected

🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost/server/v8

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

Mattermost versions 10.8.x <= 10.8.3, 10.5.x <= 10.5.8, 9.11.x <= 9.11.17, 10.10.x <= 10.10.1, 10.9.x <= 10.9.3 fail to validate import directory path configuration which allows admin users to execute arbitrary code via malicious plugin upload to prepackaged plugins directory

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost-server`	≥ 10.8.0&&< 10.8.4	10.8.4
🐹Go	`github.com/mattermost/mattermost-server`	≥ 10.5.0&&< 10.5.9	10.5.9
🐹Go	`github.com/mattermost/mattermost-server`	≥ 9.11.0&&< 9.11.18	9.11.18
🐹Go	`github.com/mattermost/mattermost-server`	≥ 10.10.0&&< 10.10.2	10.10.2
🐹Go	`github.com/mattermost/mattermost-server`	≥ 10.9.0&&< 10.9.4	10.9.4
🐹Go	`github.com/mattermost/mattermost/server/v8`	all versions	8.0.0-20250707221302-a8fa77f107ef

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 10.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-9079 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 CVE-2025-9079 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 CVE-2025-9079. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-9079 in your dependencies?

O3 detects CVE-2025-9079 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