Skip to content
Fencer Intel
medium 4.3

CVE-2026-4055 json

Insufficient permission validation on cross-team playbook run creation

published 5mo ago modified 3mo ago also GHSA-6cfr-wp44-6qmv , GO-2026-5173 , EUVD-2026-31221

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 4%
public exploits
0
none known

Summary

Mattermost versions 11.5.x <= 11.5.1 fail to validate team-level run_create permission against the target team when creating a playbook run which allows an authenticated team member to create runs in teams where they lack permission via specifying a different team ID in the run creation API request. Mattermost Advisory ID: MMSA-2026-00629

Patch / fix

  • go github.com/mattermost/mattermost/server/v8 8.0.0-20260320113102-f2b3d1c6a945
  • Mattermost Mattermost 10.11.14, 11.4.4, 11.5.2, 11.6.0
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2026-4055 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost/server/v8
>=8.0.0-20260304132957-9f2616376582, <8.0.0-20260320113102-f2b3d1c6a945
8.0.0-20260320113102-f2b3d1c6a945
go github.com/mattermost/mattermost-server
all versions
no fix listed
go github.com/mattermost/mattermost-server/v5
all versions
no fix listed
go github.com/mattermost/mattermost-server/v6
all versions
no fix listed

Affected products

  • Mattermost Mattermost

Classification

Weakness

References

Sources

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.