CVE-2025-9079 json
Admin RCE via prepackaged plugins by way of misconfigured imports directory
published last yr. modified 21d ago also GHSA-qx3f-6vq3-8j8m , GO-2025-3977 , EUVD-2025-30242
- cvss
- 8.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- go github.com/mattermost/mattermost-server 9.11.18, 9.11.18+incompatible, 10.5.9, 10.5.9+incompatible, 10.8.4, 10.8.4+incompatible, 10.9.4, 10.9.4+incompatible, 10.10.2, 10.10.2+incompatible
- go github.com/mattermost/mattermost/server/v8 8.0.0-20250707221302-a8fa77f107ef
- Mattermost Mattermost 9.11.18, 10.5.9, 10.8.4, 10.9.4, 10.10.2, 10.11.0
- govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20251023T162509-150000.1.110.1
suse advisories SUSE-SU-2025:3799-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20250924T192141-1.1
opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2025:15576-1
Is CVE-2025-9079 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.64% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/mattermost/mattermost-server | >=10.8.0, <10.8.4 >=10.5.0, <10.5.9 >=9.11.0, <9.11.18 >=10.10.0, <10.10.2 >=10.9.0, <10.9.4 >=9.11.0+incompatible, <9.11.18+incompatible >=10.5.0+incompatible, <10.5.9+incompatible >=10.8.0+incompatible, <10.8.4+incompatible >=10.9.0+incompatible, <10.9.4+incompatible >=10.10.0+incompatible, <10.10.2+incompatible |
10.8.4 10.5.9 9.11.18 10.10.2 10.9.4 9.11.18+incompatible 10.5.9+incompatible 10.8.4+incompatible 10.9.4+incompatible 10.10.2+incompatible |
| go | github.com/mattermost/mattermost/server/v8 | <8.0.0-20250707221302-a8fa77f107ef |
8.0.0-20250707221302-a8fa77f107ef |
| go | github.com/mattermost/mattermost-server/v5 | all versions |
no fix listed |
| go | github.com/mattermost/mattermost-server/v6 | all versions |
no fix listed |
Affected products
- Mattermost Mattermost
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/mattermost/mattermost/commit/047a2c64071749367fe02d2162f6103a3d31a883
web
-
github.com
/mattermost/mattermost/commit/439464883aa16a329c23cd6274c4cca7e88e238f
web
-
github.com
/mattermost/mattermost/commit/4ff68eea0a3f3777032d31a1a82f4b1fb492a1ac
web
-
github.com
/mattermost/mattermost/commit/96665b9b98a17534fcd515982a2eb26950581e41
web
-
github.com
/mattermost/mattermost/commit/a8fa77f107efe83f09a779f8e67cbecf236b0032
web
-
github.com
/mattermost/mattermost/commit/b38e2eccda182212a8032539658723c7d87e0b7e
web
-
mattermost.com
/security-updates
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-9079
advisory
-
github.com
/mattermost/mattermost
package
-
pkg.go.dev
/vuln/GO-2025-3977
web
-
github.com
/advisories/GHSA-qx3f-6vq3-8j8m
advisory
Sources
- CVE List CVE-2025-9079
- GitHub Advisory GHSA-qx3f-6vq3-8j8m
- NVD CVE-2025-9079
- OSV GO-2025-3977
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.