Advisory record · GHSA-w9m8-p4cc-4qj9

Mattermost doesn't properly validate msgpack-encoded WebSocket frames before memory allocation

CVSS 7.5 HighEPSS 0.0034 · 27th percentile

Published by the GitHub Advisory Database at 26 May 2026, 13:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/mattermost/mattermost-serverGo>=11.6.0, <11.6.1 || >=11.5.0, <11.5.4 || >=11.4.0, <11.4.5 || >=10.11.0, <10.11.1511.6.1, 11.5.4, 11.4.5, 10.11.15
github.com/mattermost/mattermost/server/v8Go<8.0.0-20260410202636-17939826efa28.0.0-20260410202636-17939826efa2
Identifiers
GHSA-w9m8-p4cc-4qj9 · CVE-2026-5740 · GO-2026-5838
Weakness (CWE)
CWE-789
Published
26 May 2026
Updated
7 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Mattermost server versions 10.11.0 through 10.11.14, 11.4.0 through 11.4.4, 11.5.0 through 11.5.3, and 11.6.0 are affected. The server does not properly validate msgpack-encoded WebSocket frames before allocating memory. An unauthenticated remote attacker can send a crafted binary WebSocket message to the public WebSocket endpoint and crash the server process, causing an outage for all users. Upgrade to 10.11.15, 11.4.5, 11.5.4, 11.6.1, or later in the affected branch.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (Mattermost)
  • CISA KEV Not listed.
  • EPSS 0.0034, the 27th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:06 UTC First seen by agentprime
  2. 31 Oct 2026, 15:06 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.