Authenticated cross-playbook metric tampering via foreign metric IDs
Published Jul 13, 2026 · Updated Jul 13, 2026
Mattermost 10.11.0 through 10.11.19, 11.6.0 through 11.6.4, and 11.7.0 through 11.7.1 allows remote authenticated users to alter playbook metrics. The playbook import and update paths accept a foreign metric ID and update its configuration without confirming that the metric belongs to the playbook being saved. Team access is required, and the resulting write is limited to another user's playbook metric settings.
Summary
What happened
Mattermost 10.11.0 through 10.11.19, 11.6.0 through 11.6.4, and 11.7.0 through 11.7.1 allows remote authenticated users to alter playbook metrics. The playbook import and update paths accept a foreign metric ID and update its configuration without confirming that the metric belongs to the playbook being saved. Team access is required, and the resulting write is limited to another user's playbook metric settings.
The record
- CVE
- CVE-2026-6541
- Published
- Jul 13, 2026
- Updated
- Jul 13, 2026
- Vendor
- Mattermost
- Product
- Mattermost
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 13, 2026CVE publishedPublication date reported by the CVE source.
- Jul 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.11.0 <=10.11.19
- Affected versionversion=11.6.0 <=11.6.4
- Affected versionversion=11.7.0 <=11.7.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo