How severe is CVE-2026-3114?

CVE-2026-3114 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-3114?

CVE-2026-3114 affects the following packages: github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go). Ecosystems affected: Go.

How do I fix CVE-2026-3114?

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

How do I detect CVE-2026-3114 in my Go dependencies?

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.

How do I mitigate CVE-2026-3114 if there is no patch (or I can't update yet)?

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.

Is CVE-2026-3114 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-3114 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-3114?

CVE-2026-3114 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-3114?

CVE-2026-3114 is classified as CWE-409 (CWE-409). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-3114 published, and has it been updated?

CVE-2026-3114 was published on March 26, 2026 and was last updated on November 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2026-3114 — server

MEDIUM

CVE-2026-3114 is a medium-severity (CVSS 6.5) CWE-409 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.

Zip Bomb Denial of Service via Unrestricted Archive Decompression

Also known asGHSA-vhgh-g7x8-4rx8GO-2026-5663

Published

Mar 26, 2026

Updated

Nov 7, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 7, 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-3114.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

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/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8

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.4.x <= 11.4.0, 11.3.x <= 11.3.1, 11.2.x <= 11.2.3, 10.11.x <= 10.11.11 fail to validate decompressed archive entry sizes during file extraction which allows authenticated users with file upload permissions to cause a denial of service via crafted zip archives containing highly compressed entries (zip bombs) that exhaust server memory.. Mattermost Advisory ID: MMSA-2026-00598

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 11.4.0&&< 11.4.1	11.4.1`go get github.com/mattermost/mattermost/server/v8@v11.4.1`
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 11.3.0&&< 11.3.2	11.3.2`go get github.com/mattermost/mattermost/server/v8@v11.3.2`
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 11.2.0&&< 11.2.4	11.2.4`go get github.com/mattermost/mattermost/server/v8@v11.2.4`
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 10.11.0&&< 10.11.12	10.11.12`go get github.com/mattermost/mattermost/server/v8@v10.11.12`
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 8.0.0-20260105080200-d27a2195068d&&< 8.0.0-20260217110922-b7d4a1f1f59b	8.0.0-20260217110922-b7d4a1f1f59b`go get github.com/mattermost/mattermost/server/v8@v8.0.0-20260217110922-b7d4a1f1f59b`

Affected Products

1 product · 4 configurations

Application

mattermost servermattermost

≥ 11.3.0 && < 11.3.2

1 version

11.4.0

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update github.com/mattermost/mattermost/server/v8 to 11.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-3114 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

O3 Security · Impact-Aware SCA

Is CVE-2026-3114 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

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

CWE Classification

CWE-409CWE-409

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Mar 26, 2026

Last updated

Nov 7, 2026

Identifiers

CVE-2026-3114

GHSA-vhgh-g7x8-4rx8

GO-2026-5663

References

Advisorygithub.com · CVE 2026 3114.json Advisorymattermost.com · security updates Advisorynvd.nist.gov · CVE 2026 3114 Packagegithub.com · mattermost

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs affecting v8 are rated as high or higher (top: high).

CVE-2026-8823CVE-2026-6046CVE-2026-7387CVE-2026-6961CVE-2026-7184CVE-2026-6689CVE-2026-6739CVE-2026-3433

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 7, 2026

CVE-2026-3114 — server

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2026-3114 in your dependencies?