Advisory record · GHSA-9p64-jpc7-m2rp

Mattermost doesn't sanitize sensitive configuration fields before including them in support packet generation

CVSS 8.7 HighEPSS 0.0030 · 23rd percentile

Published by the GitHub Advisory Database at 18 May 2026, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/mattermost/mattermost/server/v8Go>=11.5.0, <11.5.2 || >=10.11.0, <10.11.14 || >=11.4.0, <11.4.4 || <8.0.0-20260326202606-fac92f4a71f311.5.2, 10.11.14, 11.4.4, 8.0.0-20260326202606-fac92f4a71f3
github.com/mattermost/mattermost-serverGo<5.3.2-0.20260326202606-fac92f4a71f35.3.2-0.20260326202606-fac92f4a71f3
Identifiers
GHSA-9p64-jpc7-m2rp · CVE-2026-6346 · GO-2026-5293
Weakness (CWE)
CWE-200
Published
18 May 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Mattermost server versions 11.5.0 through 11.5.1, 10.11.0 through 10.11.13, and 11.4.0 through 11.4.3 include sensitive configuration fields in support packets without sanitizing them. A Mattermost System Admin, or anyone who gets access to a support packet, can read sensitive credentials in plaintext. Upgrade to 10.11.14, 11.4.4, or 11.5.2, depending on the release line in use.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.7 High 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N CNA (Mattermost)
  • CISA KEV Not listed.
  • EPSS 0.0030, the 23rd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:07 UTC First seen by agentprime
  2. 31 Oct 2026, 15:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.