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 | 3750 days past EOL | EOL |
| 1.1 | 1.1.2 | Jun 19, 2012 | Feb 1, 2016 | 3750 days past EOL | EOL |
| 2.0 | 2.0.6 | Oct 7, 2014 | Jan 1, 2021 | 1954 days past EOL | EOL |
| 2.1 | 2.1.1 | May 19, 2015 | Jan 1, 2021 | 1954 days past EOL | EOL |
| 2.2 | 2.2.3 | Nov 17, 2015 | Jan 1, 2021 | 1954 days past EOL | EOL |
| 2.3 | 2.3.3 | May 17, 2016 | Jan 1, 2021 | 1954 days past EOL | EOL |
| 2.4 | 2.4.2 | Nov 3, 2016 | Jan 1, 2021 | 1954 days past EOL | EOL |
| 2.5 | 2.5.14 | Jun 20, 2017 | Jan 1, 2021 | 1954 days past EOL | EOL |
| 3.0 | 3.0.3 | Jan 15, 2019 | Nov 16, 2021 | 1635 days past EOL | EOL |
| 3.1 | 3.1.4 | Mar 19, 2019 | Nov 16, 2021 | 1635 days past EOL | EOL |
| 3.2 | 3.2.5 | Jun 25, 2019 | Nov 16, 2021 | 1635 days past EOL | EOL |
| 3.3 | 3.3.6 | Nov 5, 2019 | Nov 16, 2021 | 1635 days past EOL | EOL |
| 3.4 | 3.4.5 | Jul 7, 2020 | Nov 16, 2021 | 1635 days past EOL | EOL |
| 3.5 | 3.5.8.4 | Dec 15, 2020 | Nov 15, 2023 | 906 days past EOL | EOL |
| 3.6 | 3.6.6.6 | Nov 16, 2021 | Jun 26, 2024 | 682 days past EOL | EOL |
| 3.7 | 3.7.5.5 | Jun 27, 2022 | Oct 5, 2024 | 581 days past EOL | EOL |
| 3.8 | 3.8.4.4 | Oct 6, 2022 | Jan 16, 2025 | 478 days past EOL | EOL |
| 3.9 | 3.9.8.3 | Jan 17, 2023 | Nov 27, 2025 | 163 days past EOL | EOL |
| 4 | 4.9.0 | Nov 28, 2023 | Jun 23, 2027 | 410 days remaining | Active |
| 3.10 | 3.10.1.2 | Dec 19, 2023 | Nov 27, 2025 | 163 days past EOL | EOL |
| 5 | 5.4.0 | Jun 24, 2025 | Already EOL | Supported | Active |
When a Kirby 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 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →