OAuth authorization code client binding not enforced during token redemption in Mattermost
Mattermost
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost/server/v8 Go |
|
|
| github.com/mattermost/mattermost-server |
Mattermost
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost/server/v8 Go |
|
|
| github.com/mattermost/mattermost-server |
|
|
| github.com/mattermost/mattermost-server/v5 Go |
| No fix yet |
| github.com/mattermost/mattermost-server/v6 Go |
| No fix yet |
Mattermost versions 11.5.x <= 11.5.1, 10.11.x <= 10.11.13 fail to enforce client identity binding during the OAuth authorization code redemption flow which allows an authenticated OAuth client to redeem authorization codes issued to a different client via a crafted token exchange request.. Mattermost Advisory ID: MMSA-2026-00570
From the CVE record · Mattermost
Affected Mattermost versions fail to bind OAuth authorization codes to the client they were issued to during redemption. An authenticated OAuth client can use a crafted token exchange request to redeem a code issued to a different client.
Teams running Mattermost 11.5.x through 11.5.1 or 10.11.x through 10.11.13, or using the listed affected Go packages, should check their deployments.