Skip to content

Mattermost doesn't limit the size of the request body on the start meeting API endpoint

Moderate severity GitHub Reviewed Published May 18, 2026 to the GitHub Advisory Database • Updated Jun 1, 2026

Package

gomod github.com/mattermost/mattermost-plugin-msteams-meetings (Go)

Affected versions

< 1.1.1-0.20260213105619-c5892dd169de

Patched versions

1.1.1-0.20260213105619-c5892dd169de
gomod github.com/mattermost/mattermost-server (Go)
>= 11.5.0, < 11.5.2
>= 10.11.0, < 10.11.14
>= 11.4.0, < 11.4.4
11.5.2
10.11.14
11.4.4

Description

Mattermost versions 11.5.x <= 11.5.1, 10.11.x <= 10.11.13, 11.4.x <= 11.4.3 fail to limit the size of the request body on the start meeting API endpoint, which allows an authenticated attacker to cause resource exhaustion or denial of service via a crafted oversized HTTP POST request to {{/api/v1/meetings}}.. Mattermost Advisory ID: MMSA-2026-00608

References

Published by the National Vulnerability Database May 18, 2026
Published to the GitHub Advisory Database May 18, 2026
Last updated Jun 1, 2026
Reviewed Jun 1, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(15th percentile)

Weaknesses

Allocation of Resources Without Limits or Throttling

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. Learn more on MITRE.

CVE ID

CVE-2026-2325

GHSA ID

GHSA-m3p3-8frq-q7qh

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.