Skip to main content
CVE-2026-18399VulnerabilityPublished

Mattermost versions 11.7.x <= 11.7.11, 11.10.x <= 11.10.2, 11.11.x <= 11.11.1 fail to enforce the configured GitLab

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-18399· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 18 Nov 2026, 20:04 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Mattermost)CVSS 3.14.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
MattermostMattermostAffected
  • >=11.7.0 <=11.7.11
  • >=11.10.0 <=11.10.2
  • >=11.11.0 <=11.11.1
Fixed in–

AI-suggested

Until a fix is available, consider restricting GitLab account connections or limiting user permissions to reduce exposure.

Description

Certain Mattermost versions (11.7.x up to 11.7.11, 11.10.x up to 11.10.2, and 11.11.x up to 11.11.1) do not properly enforce GitLab group or namespace restrictions on the permalink code-preview feature and the {{get_projects}} MCP tool. This flaw allows an authenticated user with a connected GitLab account to access repository file content or project metadata from projects outside the intended restricted group.

References

Community reviews

Loading reviews…