What is the CVSS score of EUVD-2026-31646?

EUVD-2026-31646 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.0%.

Is there a patch available for EUVD-2026-31646?

Yes, a patch is available for EUVD-2026-31646. Update the affected software to the latest version immediately.

Mattermost EUVD-2026-31646

Q: Which versions of Mattermost are affected by EUVD-2026-31646?

Server process termination in Mattermost is achievable by any authenticated user via a crafted outgoing webhook callback response that contains a null attachment entry - exploiting the server's…. A patch is available.

| CVE-2026-4915 MEDIUM

Improper Check for Unusual or Exceptional Conditions (CWE-754)

2026-05-25 Mattermost

GHSA-5gmf-x7hg-97wf

Denial Of Service Mattermost

6.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.5 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

Analysis Generated

Jun 08, 2026 - 12:45 vuln.today

DescriptionCVE.org

Mattermost versions 11.6.x <= 11.6.0, 11.5.x <= 11.5.3, 11.4.x <= 11.4.4, 10.11.x <= 10.11.14 fail to filter nil elements from outgoing webhook attachment payloads before processing, which allows an authenticated user to cause a denial of service (server process termination) via a crafted webhook callback response containing a null attachment entry.. Mattermost Advisory ID: MMSA-2026-00641

AnalysisAI

Server process termination in Mattermost is achievable by any authenticated user via a crafted outgoing webhook callback response that contains a null attachment entry - exploiting the server's failure to filter nil elements from attachment payloads before processing (CWE-754). Affected release trains span 10.11.x through 11.6.x, covering a wide installed base. No public exploit exists and EPSS is extremely low at 0.04% (12th percentile), but the availability impact is rated High by CVSS and the attack requires only low-privilege authentication over the network with no user interaction, making this a meaningful insider or compromised-account threat capable of triggering a full service outage.

Technical ContextAI

Mattermost is an open-source team messaging platform written primarily in Go. Its outgoing webhook feature allows channels to POST data to external URLs and process the returned payloads. The root cause is CWE-754 (Improper Check for Unusual or Exceptional Conditions): the server-side attachment payload processing pipeline does not validate or filter nil elements from the webhook callback response's attachment array before iterating over it. In Go, dereferencing a nil pointer or ranging over a structure containing nil elements without guards causes a runtime panic, which terminates the server process. CPE cpe:2.3:a:mattermost:mattermost applies broadly across versions. The vulnerability is specific to the outgoing webhook attachment handling code path, not the broader messaging or API surface.

RemediationAI

Upgrade Mattermost to a fixed release above the affected version ceilings for each supported branch: the next release above 10.11.14 in the 10.11.x train, above 11.4.4 in the 11.4.x train, above 11.5.3 in the 11.5.x train, and above 11.6.0 in the 11.6.x train. Exact patched version numbers are not explicitly enumerated in the available data and should be confirmed directly at https://mattermost.com/security-updates (MMSA-2026-00641). If immediate patching is not possible, a compensating control is to restrict or disable the outgoing webhooks feature via the System Console (Site Configuration > Integrations > Enable Outgoing Webhooks), which eliminates the vulnerable code path entirely; however, this disables all outgoing webhook integrations and may impact automation workflows. Alternatively, restrict outgoing webhook creation to trusted, highly privileged roles only, reducing the pool of users who can trigger the vulnerable path. Network-layer blocking of the webhook callback port does not fully mitigate the issue, as the null payload can be delivered by any server the webhook is pointed to.