CVE-2026-16046: Mattermost versions 11.7.x <= 11.7.6, 10.11.x <= 10.11.21 fail to enforce run-state validation on write operations for finished playbook runs which
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
AI-suggested
Until a patch or official fix is available, restrict participant privileges where possible to limit unauthorized modifications to finished playbook runs.
Description
Mattermost versions 11.7.x up to 11.7.6 and 10.11.x up to 10.11.21 contain a vulnerability where run-state validation is not enforced on write operations for finished playbook runs. This flaw allows participants of a run to modify certain aspects such as status, checklists, retrospective content, ownership, and participants on completed runs via REST and GraphQL API requests.