Mattermost Playbooks fails to validate the uniqueness and quantity of task actions in github.com/mattermost/mattermost-plugin-playbooks
Published 24 Apr 2025 · Updated 4 Feb 2026
Is your project on an affected github.com/mattermost/mattermost-plugin-playbooks?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- All versions
- Fixed in
- No fix released
- Affected
- <1.41.0
- Fixed in
- 1.41.0
go get github.com/mattermost/mattermost-plugin-playbooks@v1.41.0- Affected
- >=9.11.0+incompatible
- Fixed in
- No fix released
- Affected
- >=10.4.0+incompatible
- Fixed in
- No fix released
- Affected
- >=10.5.0+incompatible
- Fixed in
- No fix released
- Affected
- All versions
- Fixed in
- No fix released
- Affected
- All versions
- Fixed in
- No fix released
- Affected
- All versions
- Fixed in
- No fix released
- Affected
- All versions
- Fixed in
- No fix released
- Affected
- All versions
- Fixed in
- No fix released
- Affected
- <8.0.0-20250218121836-2b5275d87136
- Fixed in
- 8.0.0-20250218121836-2b5275d87136
go get github.com/mattermost/mattermost/server/v8@v8.0.0-20250218121836-2b5275d87136Details
Mattermost Playbooks fails to validate the uniqueness and quantity of task actions in github.com/mattermost/mattermost-plugin-playbooks.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: .
Is GO-2025-3643 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/mattermost/mattermost-plugin-playbooks, and gives you the command that fixes it.
More advisories for github.com/mattermost/mattermost-plugin-playbooks
- LowCVE-2026-4286Mattermost doesn't check if {{team_id}} was being changed when updating playbooks in github.com/mattermost/mattermost-plugin-playbooks · 25 Jun 2026
- LowCVE-2026-6343Mattermost doesn't check public/private permissions in github.com/mattermost/mattermost-plugin-playbooks · 25 Jun 2026
- MediumCVE-2026-6343Mattermost doesn't check public/private permissions · 18 May 2026
- LowCVE-2026-4286Mattermost doesn't check if {{team_id}} was being changed when updating playbooks · 18 May 2026
- LowCVE-2026-26304Mattermost fails to verify run_create permission for empty playbookId in github.com/mattermost/mattermost-plugin-playbooks · 23 Mar 2026
- MediumCVE-2026-26304Mattermost fails to verify run_create permission for empty playbookId · 16 Mar 2026
References
- Advisorygithub.com/advisories/GHSA-689c-xq7x-xjwf
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-35965
- Fixgithub.com/mattermost/mattermost-plugin-playbooks/commit/bf2633dad09f5768ce2bea4b7c5ffb74050052a8
- Linkgithub.com/mattermost/mattermost/commit/2b5275d87136f07e016c8eca09a2f004b31afc8a
- Linkmattermost.com/security-updates
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.