Skip to content
Fencer Intel
low 3.7

CVE-2025-13324 json

Lack of Invalidation of Legacy Remote Cluster Invite Tokens After Confirmation

published 10mo ago modified 29d ago also GHSA-x3r8-2hmh-89f5 , GO-2025-4256 , EUVD-2025-203920

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

Mattermost versions 10.11.x <= 10.11.5, 11.0.x <= 11.0.4, 10.12.x <= 10.12.2 fail to invalidate remote cluster invite tokens when using the legacy (version 1) protocol or when the confirming party does not provide a refreshed token, which allows an attacker who has obtained an invite token to authenticate as the remote cluster and perform limited actions on shared channels even after the invitation has been legitimately confirmed.

Patch / fix

  • go github.com/mattermost/mattermost 10.11.5, 10.11.5+incompatible, 10.12.2, 10.12.2+incompatible, 11.0.4, 11.0.4+incompatible
  • go github.com/mattermost/mattermost/server/v8 8.0.0-20251031095924-e7e23b94e006
  • go github.com/mattermost/mattermost-server 11.0.4, 11.0.4+incompatible
  • Mattermost Mattermost 10.11.6, 10.12.3, 11.0.5, 11.1.0
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20251230T014957-150000.1.134.1

suse advisories SUSE-SU-2026:0037-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2025-13324 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
10mo ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost
>=10.12.0, <10.12.2
>=10.11.0-rc1, <10.11.5
>=11.0.0-alpha.1, <11.0.4
>=10.11.0-rc1+incompatible, <10.11.5+incompatible
>=10.12.0+incompatible, <10.12.2+incompatible
>=11.0.0-alpha.1+incompatible, <11.0.4+incompatible
10.12.2
10.11.5
11.0.4
10.11.5+incompatible
10.12.2+incompatible
11.0.4+incompatible
go github.com/mattermost/mattermost/server/v8
<8.0.0-20251031095924-e7e23b94e006
8.0.0-20251031095924-e7e23b94e006
go github.com/mattermost/mattermost-server
<11.0.4
<11.0.4+incompatible
11.0.4
11.0.4+incompatible
go github.com/mattermost/mattermost-server/v5
all versions
 no fix listed
go github.com/mattermost/mattermost-server/v6
all versions
 no fix listed

Affected products

  • Mattermost Mattermost

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.