NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

CVE-2026-25780 — server

MEDIUMFix: mattermost/mattermost@86797c5

CVE-2026-25780 is a medium-severity (CVSS 4.3) CWE-789 vulnerability in github.com/mattermost/mattermost/server/v8. A fix is available for github.com/mattermost/mattermost/server/v8 — see the affected versions and patch details below.

Memory Exhaustion via Malformed DOC File Upload

Also known asGHSA-xv2p-wchj-qjhpGO-2026-4733
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25780.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk+0.01%
Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk
0.00%0.29%0.58%0.87%0.1%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected
🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Mattermost versions 11.3.x <= 11.3.0, 11.2.x <= 11.2.2, 10.11.x <= 10.11.10 fail to bound memory allocation when processing DOC files which allows an authenticated attacker to cause server memory exhaustion and denial of service via uploading a specially crafted DOC file.. Mattermost Advisory ID: MMSA-2026-00581

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/mattermost/mattermost/server/v8all versions8.0.0-20260123215601-86797c508c44go get github.com/mattermost/mattermost/server/v8@v8.0.0-20260123215601-86797c508c44
🐹Gogithub.com/mattermost/mattermost-serverall versions5.3.2-0.20260123215601-86797c508c44go get github.com/mattermost/mattermost-server@v5.3.2-0.20260123215601-86797c508c44
🐹Gogithub.com/mattermost/mattermost-server≥ 10.11.0-rc1&&< 10.11.1110.11.11go get github.com/mattermost/mattermost-server@v10.11.11
🐹Gogithub.com/mattermost/mattermost-server≥ 11.2.0-rc1&&< 11.2.311.2.3go get github.com/mattermost/mattermost-server@v11.2.3
🐹Gogithub.com/mattermost/mattermost-server≥ 11.3.0-rc1&&< 11.3.111.3.1go get github.com/mattermost/mattermost-server@v11.3.1

Affected Products

1 product · 3 configurations
Application
mattermost servermattermost
≥ 11.3.0 && < 11.3.1
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost/server/v8, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/mattermost/mattermost/server/v8 to 8.0.0-20260123215601-86797c508c44 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25780 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability is rated as having a Moderate impact because triggering the resource exhaustion requires established user authentication and results only in an availability disruption rather than arbitrary code execution or confidentiality loss. Red Hat Enterprise Linux does not include or ship the Mattermost…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2026-25780 (CC BY 4.0)

Frequently Asked Questions

Mattermost versions 11.3.x <= 11.3.0, 11.2.x <= 11.2.2, 10.11.x <= 10.11.10 fail to bound memory allocation when processing DOC files which allows an authenticated attacker to cause server memory exhaustion and denial of service via uploading a specially crafted DOC file.. Mattermost Advisory ID: MMSA-2026-00581
O3 Security · Impact-Aware SCA

Is CVE-2026-25780 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2026-25780: server DoS — Fix Available