What is CVE-2026-4915?

CVE-2026-4915 is a medium-severity security vulnerability in github.com/mattermost/mattermost-server (go), affecting versions = 11.6.0. It is fixed in 11.6.1, 11.5.4, 11.4.5, 10.11.15, 8.0.0-20260407102538-faa7d75b4ea0.

How severe is CVE-2026-4915?

CVE-2026-4915 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2026-4915?

github.com/mattermost/mattermost-server (go) versions = 11.6.0; github.com/mattermost/mattermost/server/v8 (go) versions < 8.0.0-20260407102538-faa7d75b4ea0.

Is CVE-2026-4915 exploitable, and should I be worried?

Whether CVE-2026-4915 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-4915 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-4915 in github.com/mattermost/mattermost-server | Intelligent Application Security

Q: Is there a fix for CVE-2026-4915?

Yes. CVE-2026-4915 is fixed in 11.6.1, 11.5.4, 11.4.5, 10.11.15, 8.0.0-20260407102538-faa7d75b4ea0. Upgrade to this version or later.

Q: Is CVE-2026-4915 exploitable, and should I be worried?

Whether CVE-2026-4915 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-4915 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-4915?

Upgrade: github.com/mattermost/mattermost-server to 11.6.1 or later, github.com/mattermost/mattermost-server to 11.5.4 or later, github.com/mattermost/mattermost-server to 11.4.5 or later, github.com/mattermost/mattermost-server to 10.11.15 or later, github.com/mattermost/mattermost/server/v8 to 8.0.0-20260407102538-faa7d75b4ea0 or later.

Summary

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

Impact

CVE-2026-4915 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.6.1, 11.5.4, 11.4.5, 10.11.15, 8.0.0-20260407102538-faa7d75b4ea0); upgrading removes the vulnerable code path.

Affected versions

github.com/mattermost/mattermost-server (= 11.6.0) github.com/mattermost/mattermost-server (>= 11.5.0, < 11.5.4) github.com/mattermost/mattermost-server (>= 11.4.0, < 11.4.5) github.com/mattermost/mattermost-server (>= 10.11.0, < 10.11.15) github.com/mattermost/mattermost/server/v8 (< 8.0.0-20260407102538-faa7d75b4ea0)

Security releases

github.com/mattermost/mattermost-server → 11.6.1 (go) github.com/mattermost/mattermost-server → 11.5.4 (go) github.com/mattermost/mattermost-server → 11.4.5 (go) github.com/mattermost/mattermost-server → 10.11.15 (go) github.com/mattermost/mattermost/server/v8 → 8.0.0-20260407102538-faa7d75b4ea0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

github.com/mattermost/mattermost-server to 11.6.1 or later; github.com/mattermost/mattermost-server to 11.5.4 or later; github.com/mattermost/mattermost-server to 11.4.5 or later; github.com/mattermost/mattermost-server to 10.11.15 or later; github.com/mattermost/mattermost/server/v8 to 8.0.0-20260407102538-faa7d75b4ea0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-4915? CVE-2026-4915 is a medium-severity security vulnerability in github.com/mattermost/mattermost-server (go), affecting versions = 11.6.0. It is fixed in 11.6.1, 11.5.4, 11.4.5, 10.11.15, 8.0.0-20260407102538-faa7d75b4ea0.
How severe is CVE-2026-4915? CVE-2026-4915 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2026-4915?
- github.com/mattermost/mattermost-server (go) (versions = 11.6.0)
- github.com/mattermost/mattermost/server/v8 (go) (versions < 8.0.0-20260407102538-faa7d75b4ea0)
Is there a fix for CVE-2026-4915? Yes. CVE-2026-4915 is fixed in 11.6.1, 11.5.4, 11.4.5, 10.11.15, 8.0.0-20260407102538-faa7d75b4ea0. Upgrade to this version or later.
Is CVE-2026-4915 exploitable, and should I be worried? Whether CVE-2026-4915 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-4915 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-4915?
- Upgrade github.com/mattermost/mattermost-server to 11.6.1 or later
- Upgrade github.com/mattermost/mattermost-server to 11.5.4 or later
- Upgrade github.com/mattermost/mattermost-server to 11.4.5 or later
- Upgrade github.com/mattermost/mattermost-server to 10.11.15 or later
- Upgrade github.com/mattermost/mattermost/server/v8 to 8.0.0-20260407102538-faa7d75b4ea0 or later

Other vulnerabilities in github.com/mattermost/mattermost-server

CVE-2026-4915 CVE-2026-28735 CVE-2026-5308 CVE-2026-3473 CVE-2026-5740