Mattermost doesn't validate the TIFF IFD offset in the image header before allocating memoryGHSA-37j2-3vv8-cf24
MEDIUMFix: mattermost/mattermost@d37c2d9GHSA-37j2-3vv8-cf24 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in github.com/mattermost/mattermost-server. A fix is available for github.com/mattermost/mattermost-server — see the affected versions and patch details below.
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 GHSA-37j2-3vv8-cf24.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-37j2-3vv8-cf24 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 384,189 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-serverReal-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.6.x <= 11.6.0, 11.5.x <= 11.5.2, 11.5.x <= 11.5.3, 11.4.x <= 11.4.4, 10.11.x <= 10.11.14 fail to validate the TIFF IFD offset in the image header before allocating memory, which allows authenticated users with file upload or posting permissions to cause a denial of service (server OOM) via uploading a crafted TIFF file or posting a URL that serves one.. Mattermost Advisory ID: MMSA-2026-00648
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 11.6.0&&< 11.6.1 | 11.6.1go get github.com/mattermost/mattermost-server@v11.6.1 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 11.5.0&&< 11.5.4 | 11.5.4go get github.com/mattermost/mattermost-server@v11.5.4 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 11.4.0&&< 11.4.5 | 11.4.5go get github.com/mattermost/mattermost-server@v11.4.5 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 10.11.0&&< 10.11.15 | 10.11.15go get github.com/mattermost/mattermost-server@v10.11.15 |
Affected Products
mattermost servermattermostDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost-server to 11.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-37j2-3vv8-cf24 is resolved across your whole dependency graph.
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.
Frequently Asked Questions
Is GHSA-37j2-3vv8-cf24 in your dependencies?
Find it across Go, including transitive dependencies.