Skip to content
Noroxi
CVE-2024-22091· NVD / CVE Program· CNA Mattermost

Excessive resource consumption due to lack to request path size limits

Mattermost versions 8.1.x <= 8.1.10, 9.6.x <= 9.6.0, 9.5.x <= 9.5.2 and 8.1.x <= 8.1.11 fail to limit the size of a request path that includes user inputs which allows an attacker to cause excessive resource consumption, possibly leading to a DoS via sending large request paths

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Apr 26, 2024
Updated
Jun 17, 2026
EPSS
0.5% · 43th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.5
CNA · Mattermost
3.1
3.4 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
mattermostmattermost server

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • mattermost mattermost server8.1.0 and later · before 8.1.12
  • mattermost mattermost server9.5.0 and later · before 9.5.3
  • mattermost mattermost server9.6.0 and later · before 9.6.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Mattermost). Independent of NVD's CPE analysis and usually ahead of it.

  • Mattermost Mattermost

    • 9.7.0, 8.1.11, 9.6.1, 9.5.3, 8.1.12not affected
    • 9.6.0affected
    • 8.1.0 and later · up to and including 8.1.10affected · semver
    • 9.5.0 and later · up to and including 9.5.2affected · semver
    • 8.1.0 and later · up to and including 8.1.11affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/mattermost/mattermost-serverfrom 8.1.0 · before 8.1.128.1.12
Gogithub.com/mattermost/mattermost-serverfrom 8.1.0+incompatible · before 8.1.12+incompatible8.1.12+incompatible
Gogithub.com/mattermost/mattermost-serverfrom 9.5.0 · before 9.5.39.5.3
Gogithub.com/mattermost/mattermost-serverfrom 9.5.0+incompatible · before 9.5.3+incompatible9.5.3+incompatible
Gogithub.com/mattermost/mattermost-serverfrom 9.6.0-rc1 · before 9.6.19.6.1
Gogithub.com/mattermost/mattermost-serverfrom 9.6.0-rc1+incompatible · before 9.6.1+incompatible9.6.1+incompatible

Same product

mattermost: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-4858Path traversal in integration action URL leading to arbitrary API execution via system admin’s auth token.
    39Monitor
  • CVE-2025-12421Account Takeover via Code Exchange Endpoint
    39Monitor
  • CVE-2025-12419Account takeover on OAuth/OpenID-enabled servers
    39Monitor
  • CVE-2025-4981Path Traversal Leading to RCE by Any Authenticated Mattermost User
    39Monitor
  • CVE-2023-6458Client side path traversal due to lack of route parameters validation
    39Monitor
  • CVE-2017-18920An issue was discovered in Mattermost Server before 3.6.2.
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/mattermost/mattermost-server8.1.12Package registry (OSV)
Go:github.com/mattermost/mattermost-server8.1.12+incompatiblePackage registry (OSV)
Go:github.com/mattermost/mattermost-server9.5.3Package registry (OSV)
Go:github.com/mattermost/mattermost-server9.5.3+incompatiblePackage registry (OSV)
Go:github.com/mattermost/mattermost-server9.6.1Package registry (OSV)
Go:github.com/mattermost/mattermost-server9.6.1+incompatiblePackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-45847136 days apartPlaybook Plugin Crash via Run Checklist
    30Monitor
  • CVE-2023-5330200 days apartDenial of Service via Opengraph Data Cache
    30Monitor
  • CVE-2024-41830 days apartMattermost versions 8.1.x before 8.1.12, 9.6.x before 9.6.1, 9.5.x before 9.5.3, 9.4.x before 9.4.5 fail to limit the number of active sessi
    26Monitor
  • CVE-2024-2894921 days apartDoS via a large number of User Preferences
    26Monitor
  • CVE-2024-2805342 days apartResource Exhaustion via the Invitation Feature
    26Monitor
  • CVE-2024-2498857 days apartExcessive resource consumption when sending long emoji names in user custom status
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

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

nvd-primary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
function expand(node) {  return node.children.map(expand);}

Fixed

ts
const MAX_DEPTH = 32;function expand(node, depth = 0) {  if (depth > MAX_DEPTH) throw new Error("too deep");  return node.children.map((c) => expand(c, depth + 1));}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records