Synced 07 Nov 2026 15:45 UTC Account
← Mastodon

Mastodon vulnerabilities: known CVEs & security history

Mastodon · Comms / Social · 5 tracked CVEs · 0 actively exploited · updated November 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Mastodon release lines — 5 in total. A CVE here doesn't mean your version is affected — check Mastodon's current status and the safe version to run.

5
known CVEs
0
actively exploited (KEV)
0
critical severity
0
ransomware-linked

Known Mastodon CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2025-62605 medium 4.3 0% 2025
CVE-2025-62176 medium 4.3 0% 2025
CVE-2025-62175 medium 4.3 0% 2025
CVE-2025-67500 low 3.7 0% 2025
CVE-2025-62174 low 3.5 0% 2025

Is my Mastodon version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Mastodon version → · Monitor Mastodon for new CVEs →

Mastodon vulnerabilities — frequently asked

How many known vulnerabilities does Mastodon have?

IsItPatched tracks 5 CVEs for Mastodon. 0 are critical-severity and 0 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Mastodon have any actively-exploited vulnerabilities?

None of Mastodon's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Mastodon vulnerability?

Among tracked issues, CVE-2025-62605 (MEDIUM, CVSS 4.3) ranks highest — a CWE-754 weakness.

Is Mastodon safe to use?

It depends on the version. The latest supported Mastodon release (4.7.3) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Mastodon security status · Mastodon end-of-life · actively-exploited CVEs. Always verify against Mastodon's advisories — see our disclaimer.