Skip to content
Fencer Intel
critical 10.0

CVE-2023-36460 in the critical feed json

Mastodon vulnerable to arbitrary file creation through media attachments

published 3y ago modified 2mo ago also BIT-mastodon-2023-36460 , EUVD-2023-40422 , GHSA-9928-3cp5-93fm

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

Summary

Mastodon is a free, open-source social network server based on ActivityPub. Starting in version 3.5.0 and prior to versions 3.5.9, 4.0.5, and 4.1.3, attackers using carefully crafted media files can cause Mastodon's media processing code to create arbitrary files at any location. This allows attackers to create and overwrite any file Mastodon has access to, allowing Denial of Service and arbitrary Remote Code Execution. Versions 3.5.9, 4.0.5, and 4.1.3 contain a patch for this issue.

Patch / fix

  • bitnami mastodon 3.5.9, 4.0.5, 4.1.3
  • joinmastodon mastodon 3.5.9, 4.0.5, 4.1.3

Is CVE-2023-36460 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

40.11% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OSV 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami mastodon
>=3.5.0, <3.5.9
>=4.0.0, <4.0.5
>=4.1.0, <4.1.3
3.5.9
4.0.5
4.1.3

Affected products

  • mastodon mastodon

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel 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.