MediumGHSA-mh4x-rmrx-3hp4CVE-2026-3590GO-2026-5507

Mattermost has session spoofing due to lack of single-use consumption of guest magic link tokens enforcement

Published 17 Apr 2026 · Updated 25 Jun 2026

Is your project on an affected github.com/mattermost/mattermost/server/v8?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=8.0.0-20250721062209-4952acea88ce <8.0.0-20250723052842-4cb8d8940332
Fixed in
8.0.0-20250723052842-4cb8d8940332
Update to the fixed version for your release line, for example:go get github.com/mattermost/mattermost/server/v8@v8.0.0-20250723052842-4cb8d8940332
Affected
>=10.11.0-rc1 <10.11.13
Fixed in
10.11.13
Update to the fixed version for your release line, for example:go get github.com/mattermost/mattermost-server@v10.11.13
Affected
>=11.5.0-rc1 <11.5.0
Fixed in
11.5.0
Update to the fixed version for your release line, for example:go get github.com/mattermost/mattermost-server@v11.5.0
Affected
>=11.4.0-rc1 <11.4.3
Fixed in
11.4.3
Update to the fixed version for your release line, for example:go get github.com/mattermost/mattermost-server@v11.4.3
Affected
>=11.3.0-rc1 <11.3.3
Fixed in
11.3.3
Update to the fixed version for your release line, for example:go get github.com/mattermost/mattermost-server@v11.3.3

Details

Mattermost versions 10.11.x <= 10.11.12, 11.5.x <= 11.5.0, 11.4.x <= 11.4.2, 11.3.x <= 11.3.2 fail to enforce atomic single-use consumption of guest magic link tokens, which allows an attacker with access to a valid magic link to establish multiple independent authenticated sessions via concurrent requests. Mattermost Advisory ID: MMSA-2026-00624.

Is GHSA-mh4x-rmrx-3hp4 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
All 393 advisories for github.com/mattermost/mattermost/server/v8

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.