CVE-2026-6739
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMattermost versions 11.6.x <= 11.6.1, 11.5.x <= 11.5.4, 10.11.x <= 10.11.15, 10.11.x <= 10.11.16 fail to require system-level permission when patching protected default system roles, which allows authenticated users with delegated user-management permissions to escalate privileges by altering built-in role permissions via the role patch API.. Mattermost Advisory ID: MMSA-2026-00656
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMattermost fails to enforce system-level permission checks when patching protected default system roles through the role patch API. Authenticated users with delegated user-management permissions can exploit this to escalate privileges by modifying built-in role permissions, bypassing the required system-level authorization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 10.11.0, < 10.11.17>= 11.5.0, < 11.5.5>= 11.6.0, < 11.6.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mattermost Server versionQuery the /api/v4/system/about endpoint or check the Mattermost logs for the ServerVersion fieldAffected if The version falls within any of these ranges: 10.11.0-10.11.16, 11.5.0-11.5.4, or 11.6.0-11.6.1
-
Audit user accounts with delegated user-management permissionsQuery the /api/v4/users endpoint and examine the roles field for users assigned permissions that include user_management roles (such as system_user_manager, system_admin, or custom roles with user management capabilities)Affected if Any user account possesses delegated user-management permissions and the server version is vulnerable
-
Review current state of protected default system rolesQuery the /api/v4/roles endpoint to retrieve all system roles and compare their current permission sets against known defaults, particularly checking for unexpected modifications to roles named 'system_admin', 'system_user_manager', or other built-in rolesAffected if Any protected default system role contains permissions that were not assigned by default or shows recent modification timestamps you did not authorize
-
Check API access logs for role patch operationsSearch server and API logs for POST or PATCH requests to /api/v4/roles/{role_id}/patch or similar endpoints that modify role permissions, filtering for requests made by non-system-admin usersAffected if There are logged role patch API calls from users who do not hold full system administrator privileges
You are affected if your Mattermost Server version is 10.11.0-10.11.16, 11.5.0-11.5.4, or 11.6.0-11.6.1 AND you have users with delegated user-management permissions who could access the role patch API.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.11.1711.5.511.6.2
Upgrade to patched versions of Mattermost (11.6.2+, 11.5.5+, 10.11.16+, 10.11.17+) or restrict delegated user-management permissions until patches can be applied.
Upgrade to Mattermost Server 10.11.17 (or later 10.11.x), 11.5.5 (or later 11.5.x), or 11.6.2 (or later 11.6.x) based on your current branch
- 1. Identify the currently running Mattermost Server version using the system console or CLI
- 2. Based on your current major version (10.11.x, 11.5.x, or 11.6.x), plan upgrade to the minimum fixed version: 10.11.17, 11.5.5, or 11.6.2 respectively
- 3. Review Mattermost upgrade documentation and ensure backup of database and configuration files
- 4. Schedule maintenance window as upgrades may require brief service interruption
- 5. Perform upgrade following Mattermost standard upgrade procedures for your deployment type (helm chart, docker, or manual)
- 6. After upgrade, verify the system is operational and test role-based access controls
- 7. Confirm the role patch API now correctly requires system-level permissions for protected default system roles
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6739 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6739 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data