Kirby End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Kirby versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.9 | Jan 9, 2012 | Feb 1, 2016 | 3795 days past EOL | EOL |
| 1.1 | 1.1.2 | Jun 19, 2012 | Feb 1, 2016 | 3795 days past EOL | EOL |
| 2.0 | 2.0.6 | Oct 7, 2014 | Jan 1, 2021 | 1999 days past EOL | EOL |
| 2.1 | 2.1.1 | May 19, 2015 | Jan 1, 2021 | 1999 days past EOL | EOL |
| 2.2 | 2.2.3 | Nov 17, 2015 | Jan 1, 2021 | 1999 days past EOL | EOL |
| 2.3 | 2.3.3 | May 17, 2016 | Jan 1, 2021 | 1999 days past EOL | EOL |
| 2.4 | 2.4.2 | Nov 3, 2016 | Jan 1, 2021 | 1999 days past EOL | EOL |
| 2.5 | 2.5.14 | Jun 20, 2017 | Jan 1, 2021 | 1999 days past EOL | EOL |
| 3.0 | 3.0.3 | Jan 15, 2019 | Nov 16, 2021 | 1680 days past EOL | EOL |
| 3.1 | 3.1.4 | Mar 19, 2019 | Nov 16, 2021 | 1680 days past EOL | EOL |
| 3.2 | 3.2.5 | Jun 25, 2019 | Nov 16, 2021 | 1680 days past EOL | EOL |
| 3.3 | 3.3.6 | Nov 5, 2019 | Nov 16, 2021 | 1680 days past EOL | EOL |
| 3.4 | 3.4.5 | Jul 7, 2020 | Nov 16, 2021 | 1680 days past EOL | EOL |
| 3.5 | 3.5.8.4 | Dec 15, 2020 | Nov 15, 2023 | 951 days past EOL | EOL |
| 3.6 | 3.6.6.6 | Nov 16, 2021 | Jun 26, 2024 | 727 days past EOL | EOL |
| 3.7 | 3.7.5.5 | Jun 27, 2022 | Oct 5, 2024 | 626 days past EOL | EOL |
| 3.8 | 3.8.4.4 | Oct 6, 2022 | Jan 16, 2025 | 523 days past EOL | EOL |
| 3.9 | 3.9.8.3 | Jan 17, 2023 | Nov 27, 2025 | 208 days past EOL | EOL |
| 4 | 4.9.4 | Nov 28, 2023 | Jun 23, 2027 | 365 days remaining | Active |
| 3.10 | 3.10.1.2 | Dec 19, 2023 | Nov 27, 2025 | 208 days past EOL | EOL |
| 5 | 5.4.4 | Jun 24, 2025 | TBD | Supported | Active |
What does Kirby end of life mean for your organization?
When a version of Kirby 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 Kirby 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Kirby versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →