CVE-2026-6346 is a high-severity (CVSS 8.7) Information Exposure vulnerability in github.com/mattermost/mattermost/server/v8. A fix is available for github.com/mattermost/mattermost/server/v8 — see the affected versions and patch details below.
Sensitive credentials exposed in plaintext in Mattermost support packets
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-6346.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-6346 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 380,526 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost-serverReal-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 11.5.x <= 11.5.1, 10.11.x <= 10.11.13, 11.4.x <= 11.4.3 fail to sanitize sensitive configuration fields before including them in support packet generation, which allows a Mattermost System Admin or any party with access to a support packet to obtain sensitive credentials in plaintext via downloading a support packet from the System Console.. Mattermost Advisory ID: MMSA-2026-00607
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 11.5.0&&< 11.5.2 | 11.5.2go get github.com/mattermost/mattermost/server/v8@v11.5.2 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.11.0&&< 10.11.14 | 10.11.14go get github.com/mattermost/mattermost/server/v8@v10.11.14 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 11.4.0&&< 11.4.4 | 11.4.4go get github.com/mattermost/mattermost/server/v8@v11.4.4 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | all versions | 8.0.0-20260326202606-fac92f4a71f3go get github.com/mattermost/mattermost/server/v8@v8.0.0-20260326202606-fac92f4a71f3 |
| 🐹Go | github.com/mattermost/mattermost-server | all versions | 5.3.2-0.20260326202606-fac92f4a71f3go get github.com/mattermost/mattermost-server@v5.3.2-0.20260326202606-fac92f4a71f3 |
Affected Products
mattermost servermattermostDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost/server/v8, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost/server/v8 to 11.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-6346 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2026-6346 in your dependencies?
Find it across Go, including transitive dependencies.