Skip to content
Fencer Vulns
low 3.1

CVE-2025-14822 json

DoS from quadratic complexity in model.ParseHashtags

published 2026-01-16 9 mo ago modified 2026-06-17 4 mo ago also GHSA-9r42-rhw3-2222 , GO-2026-4325 , EUVD-2026-2917

cvss
3.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

Mattermost versions 10.11.x <= 10.11.8 fail to validate input size before processing hashtags which allows an authenticated attacker to exhaust CPU resources via a single HTTP request containing a post with thousands space-separated tokens

Patch / fix

  • go github.com/mattermost/mattermost-server 10.11.9, 10.11.9+incompatible, 11.2.0, 11.2.0+incompatible
  • Mattermost Mattermost 10.11.9, 11.2.0
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260226T182644-150000.1.149.1

suse advisories SUSE-SU-2026:0757-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9 mo ago

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost-server
>=10.11.0, <10.11.9
>=11.0.0, <11.2.0
>=10.11.0+incompatible, <10.11.9+incompatible
>=11.0.1+incompatible, <11.2.0+incompatible
10.11.9
11.2.0
10.11.9+incompatible
11.2.0+incompatible

Affected products

  • Mattermost Mattermost

Classification

Weakness
  • CWE-407 Inefficient Algorithmic Complexity
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.