CVE-2026-23963
BaseFortify
Publication date: 2026-01-22
Last updated on: 2026-02-02
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| joinmastodon | mastodon | to 4.3.18 (exc) |
| joinmastodon | mastodon | From 4.4.0 (inc) to 4.4.12 (exc) |
| joinmastodon | mastodon | From 4.5.0 (inc) to 4.5.5 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-770 | The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Mastodon versions prior to v4.3.18, v4.4.12, and v4.5.5 occurs because the server does not enforce maximum length limits on list names, filter names, and filter keywords. This allows any local user to set arbitrarily long strings for these fields, which can lead to excessive consumption of storage and computing resources. Users can also make their own web interface unusable, either intentionally or by unknowingly approving a malicious API client. The issue is due to allocation of resources without limits or throttling. [1]
How can this vulnerability impact me? :
The vulnerability can cause disproportionate usage of storage and computing resources on the Mastodon server, potentially degrading performance. Additionally, a user can render their own web interface unusable. However, it does not impact confidentiality or integrity, and the availability impact is low. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade your Mastodon server to version v4.3.18, v4.4.12, or v4.5.5 or later, as these versions have patched the issue by enforcing maximum length limits on list names, filter names, and filter keywords. [1]