CISA list

Mastodon versions

Mastodon: update to 4.7.6, 4.6.12, 4.5.22 or 4.4.29. 4.3 and older have reached end of life in the lifecycle data.

Data: .

Which Mastodon branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.

Which Mastodon branch to run
BranchStatusNewest safe releaseUpgrade to
4.7Fixes, no end date announced4.7.64.7.6 (this branch)
4.63 CVE records that this page readsFixes, no end date announced4.6.124.6.12 (this branch)
4.521 CVE records that this page readsFixes until 20 February 20274.5.224.5.22 (this branch)
4.423 CVE records that this page readsFixes until 17 December 20264.4.294.4.29 (this branch)
4.317 CVE records that this page readsEnded on 6 May 2026None, the branch has ended4.4.29 (move to 4.4)
4.212 CVE records that this page readsEnded on 8 January 2026None, the branch has ended4.4.29 (move to 4.4)
4.112 CVE records that this page readsEnded on 8 April 2025None, the branch has ended4.4.29 (move to 4.4)
4.010 CVE records that this page readsEnded on 31 October 2023None, the branch has ended4.4.29 (move to 4.4)
3.59 CVE records that this page readsEnded on 31 December 2023None, the branch has ended4.4.29 (move to 4.4)
3.4Ended on 6 November 2022None, the branch has ended4.4.29 (move to 4.4)
3.3Ended on 26 May 2022None, the branch has ended4.4.29 (move to 4.4)
3.2Ended, date not knownNone, the branch has ended4.4.29 (move to 4.4)
3.1Ended, date not knownNone, the branch has ended4.4.29 (move to 4.4)
3.0Ended, date not knownNone, the branch has ended4.4.29 (move to 4.4)
2Ended, date not knownNone, the branch has ended4.4.29 (move to 4.4)
1Ended, date not knownNone, the branch has ended4.4.29 (move to 4.4)

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

This page reads 44 CVE records that the CVE Numbering Authority GitHub_M (as the CVE List names it) published and that name Mastodon. The fixes are from the 40 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

No release of a branch that has ended is called safe here.

Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.

Some records give a range that starts in an older branch and ends in a newer one. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the older branches it runs across. Only a range that runs across branches that have all ended is placed: a range that reaches a branch that still gets fixes would name that branch's newest release as affected, which a project that also fixes its older branches does not mean. Such a record is named at the end of the page.

A range that holds only pre-releases (alphas, betas and release candidates) is left out. A record whose fix is a release candidate says so in its row, and the release candidate is not listed as a release.

4 records are not placed on a branch, so no branch or release row counts them: CVE-2023-42450, CVE-2024-25619, CVE-2026-25540 and CVE-2026-47777.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)