CVE-2026-28732

Mattermost versions 11.5.x <= 11.5.1, 10.11.x <= 10.11.13, 11.4.x <= 11.4.3 Fail to enforce slash command trigger-word uniqueness during command updates which allows an authenticated team member with Manage Own Slash Commands permission to hijack and impersonate existing system or custom slash commands via editing their own slash command trigger to an already-registered trigger through the command update API. Mattermost Advisory ID: MMSA-2026-00597

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-28732 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.5.2, 10.11.14, 11.4.4, 8.0.0-20260306123948-f5fe8ded6b63, 5.3.2-0.20260306123948-f5fe8ded6b63); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-28732? CVE-2026-28732 is a medium-severity incorrect authorization vulnerability in github.com/mattermost/mattermost/server/v8 (go), affecting versions >= 11.5.0, < 11.5.2. It is fixed in 11.5.2, 10.11.14, 11.4.4, 8.0.0-20260306123948-f5fe8ded6b63, 5.3.2-0.20260306123948-f5fe8ded6b63. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-28732? CVE-2026-28732 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-28732?
   • github.com/mattermost/mattermost/server/v8 (go) (versions >= 11.5.0, < 11.5.2)
   • github.com/mattermost/mattermost-server (go) (versions < 5.3.2-0.20260306123948-f5fe8ded6b63)
4. Is there a fix for CVE-2026-28732? Yes. CVE-2026-28732 is fixed in 11.5.2, 10.11.14, 11.4.4, 8.0.0-20260306123948-f5fe8ded6b63, 5.3.2-0.20260306123948-f5fe8ded6b63. Upgrade to this version or later.
5. Is CVE-2026-28732 exploitable, and should I be worried? Whether CVE-2026-28732 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-28732 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-28732?
   • Upgrade github.com/mattermost/mattermost/server/v8 to 11.5.2 or later
   • Upgrade github.com/mattermost/mattermost/server/v8 to 10.11.14 or later
   • Upgrade github.com/mattermost/mattermost/server/v8 to 11.4.4 or later
   • Upgrade github.com/mattermost/mattermost/server/v8 to 8.0.0-20260306123948-f5fe8ded6b63 or later
   • Upgrade github.com/mattermost/mattermost-server to 5.3.2-0.20260306123948-f5fe8ded6b63 or later