Mattermost doesn't sanitize sensitive configuration fields before including them in support packet generation
Published 18 May 2026 · Updated 25 Jun 2026
Is your project on an affected github.com/mattermost/mattermost/server/v8?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=11.5.0 <11.5.2
- Fixed in
- 11.5.2
go get github.com/mattermost/mattermost/server/v8@v11.5.2- Affected
- >=10.11.0 <10.11.14
- Fixed in
- 10.11.14
go get github.com/mattermost/mattermost/server/v8@v10.11.14- Affected
- >=11.4.0 <11.4.4
- Fixed in
- 11.4.4
go get github.com/mattermost/mattermost/server/v8@v11.4.4- Affected
- <8.0.0-20260326202606-fac92f4a71f3
- Fixed in
- 8.0.0-20260326202606-fac92f4a71f3
go get github.com/mattermost/mattermost/server/v8@v8.0.0-20260326202606-fac92f4a71f3- Affected
- <5.3.2-0.20260326202606-fac92f4a71f3
- Fixed in
- 5.3.2-0.20260326202606-fac92f4a71f3
go get github.com/mattermost/mattermost-server@v5.3.2-0.20260326202606-fac92f4a71f3Details
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
Is GHSA-9p64-jpc7-m2rp in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/mattermost/mattermost/server/v8, and gives you the command that fixes it.
More advisories for github.com/mattermost/mattermost/server/v8
- LowCVE-2026-8823Mattermost has an Incorrect Authorization issue in github.com/mattermost/mattermost-server · 1 Oct 2026
- LowCVE-2026-6046Mattermost doesn't validate that a username returned during bot registration belongs to a bot account in github.com/mattermost/mattermost-server · 25 Aug 2026
- LowCVE-2026-7387Mattermost doesn't require role-management authorization when setting the scheme_admin flag on group syncable link and patch endpoints in github.com/mattermost/mattermost-server · 25 Aug 2026
- LowCVE-2026-6961Mattermost doesn't sanitize FileInfo.Name received from federated peers during shared channel file sync in github.com/mattermost/mattermost-server · 25 Aug 2026
- LowCVE-2026-7184Mattermost doesn't sanitize the Remote Cluster API response on PATCH operations in github.com/mattermost/mattermost-server · 25 Aug 2026
- LowCVE-2026-6689Mattermost doesn't enforce PermissionInviteUser when setting AllowOpenInvite or AllowedDomains during team creation in github.com/mattermost/mattermost-server · 25 Aug 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.