CVE-2026-4274 — server
MEDIUMCVE-2026-4274 is a medium-severity (CVSS 5.4) CWE-863 vulnerability in github.com/mattermost/mattermost/server/v8. A fix is available for github.com/mattermost/mattermost/server/v8 — see the affected versions and patch details below.
Insufficient authorization in shared channel membership sync grants team-level access instead of channel-level access
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-4274.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Mattermost versions 11.2.x <= 11.2.2, 10.11.x <= 10.11.10, 11.4.x <= 11.4.0, 11.3.x <= 11.3.1 fail to restrict team-level access when processing membership sync from a remote cluster, which allows a malicious remote cluster to grant a user access to an entire private team instead of only the shared channel via sending crafted membership sync messages that trigger team membership assignment. Mattermost Advisory ID: MMSA-2026-00574
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 11.4.0-rc1&&< 11.4.1 | 11.4.1go get github.com/mattermost/mattermost/server/v8@v11.4.1 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 11.3.0-rc1&&< 11.3.2 | 11.3.2go get github.com/mattermost/mattermost/server/v8@v11.3.2 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 11.2.0-rc1&&< 11.2.3 | 11.2.3go get github.com/mattermost/mattermost/server/v8@v11.2.3 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.11.0-rc1&&< 10.11.11 | 10.11.11go get github.com/mattermost/mattermost/server/v8@v10.11.11 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 8.0.0-20260105080200-d27a2195068d&&< 8.0.0-20260217110922-b7d4a1f1f59b | 8.0.0-20260217110922-b7d4a1f1f59bgo get github.com/mattermost/mattermost/server/v8@v8.0.0-20260217110922-b7d4a1f1f59b |
Affected Products
mattermost servermattermostDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost/server/v8, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost/server/v8 to 11.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-4274 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-4274 in your dependencies?
Find it across Go, including transitive dependencies.