CVE-2026-121594 json
Improper access control in the Mattermost GitLab plugin discloses confidential GitLab issues to unauthorized channel subscribers
published 12h ago modified 10h ago also EUVD-2026-130329
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Mattermost Plugins versions <=12.-1 11.11.7 11.2.10 11.1.11.0 fail to enforce the GitLab project permission check for confidential issues when the project is publicly visible which allows an authenticated user with no GitLab membership in the project to obtain the contents of confidential issues, including title, description, author, and URL via subscribing a channel to the parent public GitLab group with the confidential_issues feature and waiting for a confidential issue webhook event. Mattermost Advisory ID: MMSA-2026-00738
Patch / fix
- Mattermost Mattermost 11.7.12, 11.10.3, 11.11.2, 12.0.0
Is CVE-2026-121594 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 11h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- Mattermost Mattermost
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
mattermost.com
/security-updates
vendor-advisory
Sources
- CVE List CVE-2026-121594
- NVD CVE-2026-121594
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.