Kirby End of Life Dates

other

Cybersecurity and software maintenance are crucial aspects of development, and tracking end-of-life dates is essential for ensuring the security and stability of applications. Kirby, a platform that allows developers to track end-of-life dates, supported versions, and security patch timelines, was created to address this issue. Maintained by a team of experts, Kirby provides developers with the necessary information to plan their upgrades and migrations, helping them stay ahead of potential security risks. With its comprehensive database, Kirby has become a go-to resource for developers seeking to stay up-to-date with the latest information on software versions and their respective support timelines.

The end-of-life landscape for Kirby is characterized by a large number of versions, with a total of 21 releases, out of which 19 have already reached their end-of-life. Currently, only 2 versions are still actively supported, with the latest stable version being 5.4.3. Looking ahead, the next version to reach its end-of-life is version 4, which is scheduled to expire on 2027-06-23. This information is critical for developers who are still using older versions of Kirby, as it allows them to plan their upgrades and migrations in advance. The most recent version to reach its end-of-life was version 3.10, which expired on 2025-11-27, highlighting the importance of staying current with the latest versions and support timelines.

The security picture for Kirby is remarkably clean, with a total of 0 CVEs tracked, and no critical vulnerabilities reported. As a result, there is no most affected version, and no Known Exploited Vulnerabilities (KEV) status to report. This suggests that Kirby has been successful in maintaining a secure platform, with no known vulnerabilities that could be exploited by attackers. Nevertheless, developers should still take action to ensure the security of their applications, by regularly reviewing the support timelines for their software versions and planning their upgrades accordingly. By doing so, they can help prevent potential security risks and ensure the stability and reliability of their applications.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
5 Jun 24, 2025—No—5.6.1—Active
3.10 Dec 19, 2023—Nov 27, 2025330d ago3.10.1.2—EOL
4 Nov 28, 2023—Nov 28, 2026in 36d4.9.6—EOL soon
3.9 Jan 17, 2023—Nov 27, 2025330d ago3.9.8.3—EOL
3.8 Oct 6, 2022—Jan 16, 2025645d ago3.8.4.4—EOL
3.7 Jun 27, 2022—Oct 5, 2024748d ago3.7.5.5—EOL
3.6 Nov 16, 2021—Jun 26, 2024849d ago3.6.6.6—EOL
3.5 Dec 15, 2020—Nov 15, 20231073d ago3.5.8.4—EOL
3.4 Jul 7, 2020—Nov 16, 20211802d ago3.4.5—EOL
3.3 Nov 5, 2019—Nov 16, 20211802d ago3.3.6—EOL
3.2 Jun 25, 2019—Nov 16, 20211802d ago3.2.5—EOL
3.1 Mar 19, 2019—Nov 16, 20211802d ago3.1.4—EOL
3.0 Jan 15, 2019—Nov 16, 20211802d ago3.0.3—EOL
2.5 Jun 20, 2017—Jan 1, 20212121d ago2.5.14—EOL
2.4 Nov 3, 2016—Jan 1, 20212121d ago2.4.2—EOL
2.3 May 17, 2016—Jan 1, 20212121d ago2.3.3—EOL
2.2 Nov 17, 2015—Jan 1, 20212121d ago2.2.3—EOL
2.1 May 19, 2015—Jan 1, 20212121d ago2.1.1—EOL
2.0 Oct 7, 2014—Jan 1, 20212121d ago2.0.6—EOL
1.1 Jun 19, 2012—Feb 1, 20163917d ago1.1.2—EOL
1.0 Jan 9, 2012—Feb 1, 20163917d ago1.0.9—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions