CVE-2026-6541
Analyzed Analyzed - Analysis Complete

Authentication Bypass in Mattermost Playbook Metrics

Vulnerability report for CVE-2026-6541, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-13

Assigner: Mattermost, Inc.

Description

Mattermost versions 11.7.x <= 11.7.1, 11.6.x <= 11.6.4, 10.11.x <= 10.11.19 fail to restrict metric configuration changes to the playbook being saved, which allows an authenticated user with team access to alter another user’s playbook metric settings via a crafted import or update request with a foreign metric ID. Mattermost Advisory ID: MMSA-2026-00653

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-13
Generated
2026-08-02
AI Q&A
2026-07-14
EPSS Evaluated
2026-08-01
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
mattermost mattermost_server From 10.11.0 (inc) to 10.11.20 (exc)
mattermost mattermost_server From 11.6.0 (inc) to 11.6.5 (exc)
mattermost mattermost_server From 11.7.0 (inc) to 11.7.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-6541 is a vulnerability in Mattermost versions 11.7.x <= 11.7.1, 11.6.x <= 11.6.4, and 10.11.x <= 10.11.19. The issue occurs because the software fails to restrict metric configuration changes to the playbook being saved.

An authenticated user with team access can exploit this vulnerability by sending a crafted import or update request containing a foreign metric ID. This allows the attacker to alter another user’s playbook metric settings without proper authorization.

Detection Guidance

Detecting this vulnerability requires checking for unauthorized changes to playbook metric settings in Mattermost. Since the vulnerability allows an authenticated user to alter another user's playbook metric settings via crafted requests, you can monitor for unusual activity in the following ways:

  • Review Mattermost server logs for unexpected or frequent import/update requests related to playbook metrics. Look for requests containing foreign metric IDs or unusual patterns in metric configuration changes.
  • Check the Mattermost database or configuration files for discrepancies in playbook metric settings, particularly if metrics appear to have been modified by users who should not have access.
  • Use network monitoring tools to inspect HTTP requests to the Mattermost server, focusing on endpoints related to playbook imports or updates. Look for requests with suspicious payloads or unexpected metric IDs.

There are no specific commands provided in the context for direct detection, but you can use general logging and monitoring tools like grep, awk, or SIEM solutions to analyze logs for anomalous behavior. For example:

  • grep -i 'playbook.*metric.*update' /var/log/mattermost/mattermost.log to search for playbook metric update events in logs.
  • Use a SIEM tool to set up alerts for unusual playbook metric modifications, such as changes made by non-admin users or outside of expected workflows.
Impact Analysis

If you are using an affected version of Mattermost, this vulnerability could impact you in the following ways:

  • Unauthorized changes to playbook metric settings: An attacker with team access could modify another user’s playbook metrics, leading to incorrect or manipulated data.
  • Potential data integrity issues: Altered metrics could result in misleading analytics or operational decisions based on compromised data.
  • Exploitation requires authenticated access: The attacker must have valid credentials and team access to exploit this vulnerability.
Compliance Impact

This vulnerability may impact compliance with common standards and regulations in the following ways:

  • GDPR: If the affected playbook metrics contain or influence personal data processing, unauthorized modifications could lead to non-compliance with GDPR’s data integrity and confidentiality requirements (Article 5(1)(f)).
  • HIPAA: If the playbook metrics involve protected health information (PHI), unauthorized changes could violate HIPAA’s Security Rule, which mandates safeguards for electronic PHI (ePHI) integrity and access controls.
  • General security standards: The vulnerability represents a failure in access control (e.g., ISO 27001, NIST SP 800-53), which could affect compliance with frameworks requiring strict authorization mechanisms.
Mitigation Strategies

To mitigate this vulnerability, follow these immediate steps:

  • Upgrade Mattermost to a patched version. The affected versions are 11.7.x <= 11.7.1, 11.6.x <= 11.6.4, and 10.11.x <= 10.11.19. Apply the latest security updates provided by Mattermost to resolve the issue.
  • Restrict access to playbook metric configuration features to trusted users only. Ensure that only authorized personnel can import or update playbook metrics.
  • Monitor and audit playbook metric changes regularly to detect any unauthorized modifications. Implement logging for all metric-related actions and review logs for suspicious activity.
  • Review and enforce least-privilege access controls for Mattermost users to minimize the risk of exploitation. Limit permissions for users who do not require access to playbook metrics.
  • Subscribe to Mattermost security bulletins to stay informed about future updates and vulnerabilities. Visit https://mattermost.com/security-updates for the latest security advisories.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-6541. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart