Complete end-of-life dates, support windows, and security status for all Mastodon versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.6.1 | Feb 5, 2017 | Supported indefinitely | Supported | Active |
| 2 | 2.9.4 | Oct 18, 2017 | Supported indefinitely | Supported | Active |
| 3.0 | 3.0.2 | Oct 3, 2019 | Supported indefinitely | Supported | Active |
| 3.1 | 3.1.5 | Feb 9, 2020 | Supported indefinitely | Supported | Active |
| 3.2 | 3.2.2 | Jul 27, 2020 | Supported indefinitely | Supported | Active |
| 3.3 | 3.3.3 | Dec 27, 2020 | May 26, 2022 | 1444 days past EOL | EOL |
| 3.4 | 3.4.10 | May 16, 2021 | Nov 6, 2022 | 1280 days past EOL | EOL |
| 3.5 | 3.5.19 | Mar 30, 2022 | Dec 31, 2023 | 860 days past EOL | EOL |
| 4.0 | 4.0.15 | Nov 14, 2022 | Oct 31, 2023 | 921 days past EOL | EOL |
| 4.1 | 4.1.25 | Feb 10, 2023 | Apr 8, 2025 | 396 days past EOL | EOL |
| 4.2 | 4.2.29 | Sep 21, 2023 | Jan 8, 2026 | 121 days past EOL | EOL |
| 4.3 | 4.3.22 | Oct 8, 2024 | May 6, 2026 | 3 days past EOL | EOL |
| 4.4 | 4.4.16 | Jul 8, 2025 | Already EOL | Supported | Active |
| 4.5 | 4.5.9 | Nov 6, 2025 | Already EOL | Supported | Active |
When a Mastodon version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Mastodon should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →