MediumGHSA-c28q-m4gf-vg4qCVE-2026-6689GO-2026-6283

Mattermost doesn't enforce PermissionInviteUser when setting AllowOpenInvite or AllowedDomains during team creation

Published 12 Jun 2026 · Updated 10 Sept 2026

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

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
>=11.6.0 <11.6.1
Fixed in
11.6.1
Update to the fixed version for your release line, for example:go get github.com/mattermost/mattermost-server@v11.6.1
Affected
>=11.5.0 <11.5.5
Fixed in
11.5.5
Update to the fixed version for your release line, for example:go get github.com/mattermost/mattermost-server@v11.5.5
Affected
>=10.11.0 <10.11.17
Fixed in
10.11.17
Update to the fixed version for your release line, for example:go get github.com/mattermost/mattermost-server@v10.11.17
Affected
>=8.0.0-20250731163400-5b955468ea1e <8.0.0-20260501144115-7d6816abdfd1
Fixed in
8.0.0-20260501144115-7d6816abdfd1
Update to the fixed version for your release line, for example:go get github.com/mattermost/mattermost/server/v8@v8.0.0-20260501144115-7d6816abdfd1

Details

Mattermost versions 11.6.x <= 11.6.1, 11.5.x <= 11.5.4, 10.11.x <= 10.11.15, 10.11.x <= 10.11.16 Fail to enforce PermissionInviteUser when setting AllowOpenInvite or AllowedDomains during team creation (the check was only applied on update/patch), which allows an authenticated user holding PermissionCreateTeam but not PermissionInviteUser on the resulting team to configure invite-controlled team settings (make the team publicly joinable via open invite and/or constrain membership via allowed domains) that they are not permitted to set on an existing team via POST /api/v4/teams with allow_open_invite: true and/or a non-empty allowed_domains in the request body.. Mattermost Advisory ID: MMSA-2026-00655

Is GHSA-c28q-m4gf-vg4q 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, and gives you the command that fixes it.

More advisories for github.com/mattermost/mattermost-server

  • LowCVE-2026-8823Mattermost has an Incorrect Authorization issue in github.com/mattermost/mattermost-server · 1 Oct 2026
  • LowCVE-2026-5139Mattermost doesn't enforce administrator authorization on the {{setDefaultInstance}} call within the {{/gitlab connect}} command handler in github.com/mattermost/mattermost-server · 28 Sept 2026
  • LowCVE-2026-8074Mattermost doesn't enforce bot-specific permission checks on the user active status endpoint in github.com/mattermost/mattermost-server · 28 Sept 2026
  • LowCVE-2026-9162Mattermost doesn't invalidate cached authentication state for active WebSocket connections during global session revocation in github.com/mattermost/mattermost-server · 28 Sept 2026
  • LowCVE-2026-6673Mattermost doesn't authenticate Atlassian Connect installed callbacks, allowing a remote unauthenticated attacker to inject a rogue sharedSecret in github.com/mattermost/mattermost-server · 28 Sept 2026
  • LowCVE-2026-6062Mattermost doesn't validate channel ownership of an existing subscription before applying edits in github.com/mattermost/mattermost-server · 28 Sept 2026
All 478 advisories for github.com/mattermost/mattermost-server

References

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