GHSA-mh4x-rmrx-3hp4 CVE-2026-3590 GO-2026-5507
Mattermost has session spoofing due to lack of single-use consumption of guest magic link tokens enforcement
Medium
Go
- Severity
- 6.5 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.15%
- Chance of exploitation in the next 30 days. Higher than 4.29% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
- Fix
- Available
- 2 packages have a fixed version
Description
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.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost-server | >= 10.11.0-rc1, < 10.11.13 |
10.11.13 |
| github.com/mattermost/mattermost-server | >= 11.5.0-rc1, < 11.5.0 |
11.5.0 |
| github.com/mattermost/mattermost-server | >= 11.4.0-rc1, < 11.4.3 |
11.4.3 |
| github.com/mattermost/mattermost-server | >= 11.3.0-rc1, < 11.3.3 |
11.3.3 |
| github.com/mattermost/mattermost-server | >= 10.11.0-rc1+incompatible, < 10.11.13+incompatible>= 11.3.0-rc1+incompatible, < 11.3.3+incompatible>= 11.4.0-rc1+incompatible, < 11.4.3+incompatible>= 11.5.0-rc1+incompatible, < 11.5.0+incompatible |
10.11.13+incompatible11.3.3+incompatible11.4.3+incompatible11.5.0+incompatible |
| github.com/mattermost/mattermost-server/v5 | all versions |
No fix yet |
| github.com/mattermost/mattermost-server/v6 | all versions |
No fix yet |
| github.com/mattermost/mattermost/server/v8 | >= 8.0.0-20250721062209-4952acea88ce, < 8.0.0-20250723052842-4cb8d8940332 |
8.0.0-20250723052842-4cb8d8940332 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
github.com/mattermost/mattermost-server Go → 10.11.13
- go
go get github.com/mattermost/mattermost-server@v10.11.13 && go mod tidy
github.com/mattermost/mattermost/server/v8 Go → 8.0.0-20250723052842-4cb8d8940332
- go
go get github.com/mattermost/mattermost/server/v8@v8.0.0-20250723052842-4cb8d8940332 && go mod tidy
Severity breakdown
CVSS 3.1 6.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Weakness
CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
How to prevent it
- Implementation: The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
- Implementation: When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
- Architecture and Design: Limit the interleaving of operations on files from multiple processes.
- Implementation, Architecture and Design: If you cannot perform operations atomically and you must share access to the resource between multiple processes or threads, then try to limit the amount of time (CPU cycles) between the check and use of the resource. This will not fix the problem, but it could make it more difficult for an attack to succeed.
- Implementation: Recheck the resource after the use call to verify that the action was taken appropriately.
- Architecture and Design: Ensure that some environmental locking mechanism can be used to protect resources effectively.
- Implementation: Ensure that locking occurs before the check, as opposed to afterwards, such that the resource, as checked, is the same as it is when in use.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-xmfh-3ccg-c9fx Mattermost has an Incorrect Authorization issue | Low | Also affects github.com/mattermost/mattermost-server |
| GHSA-h998-hxxj-8q83 Mattermost doesn't invalidate cached authentication state for active WebSocket connections during global session revocation | Medium | Also affects github.com/mattermost/mattermost-server |
| GHSA-g5vr-6pgg-74qv Mattermost doesn't enforce bot-specific permission checks on the user active status endpoint | Low | Also affects github.com/mattermost/mattermost-server |
| GHSA-jqgv-39mg-7c2r Mattermost doesn't authenticate Atlassian Connect installed callbacks, allowing a remote unauthenticated attacker to inject a rogue sharedSecret | Medium | Also affects github.com/mattermost/mattermost-server |
| GHSA-mxq2-5jpg-7474 Mattermost doesn't validate channel ownership of an existing subscription before applying edits | Medium | Also affects github.com/mattermost/mattermost-server |
| GHSA-2g8v-grq3-hq2g Mattermost doesn't enforce administrator authorization on the {{setDefaultInstance}} call within the {{/gitlab connect}} command handler | Medium | Also affects github.com/mattermost/mattermost-server |
| GHSA-6hxm-w4hv-vgvw Mattermost doesn't require role-management authorization when setting the scheme_admin flag on group syncable link and patch endpoints | High | Also affects github.com/mattermost/mattermost-server |
| GHSA-9p44-r552-4wp9 Mattermost doesn't sanitize the Remote Cluster API response on PATCH operations | Medium | Also affects github.com/mattermost/mattermost-server |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor