Kirby End of Life (EOL) Dates and End of Support (EOS) Dates
Kirby end of life (EOL) and end of support (EOS) dates: 19 Kirby versions have reached EOL, including Kirby 3.10 (EOL date: Nov 27, 2025) — no longer receiving security updates or patches. Kirby 4 (A new era) reaches its End of Support date on Nov 28, 2026 — plan your upgrade path now. Kirby 5.6.4 is the current supported release. Also see Chef Supermarket lifecycle dates for related end-of-life information.
Currently Supported Kirby Releases - Active EOS/EOSL Support (1)
| Release | Supported Php Versions | Released | Security Support | Latest |
|---|---|---|---|---|
| 5 | 8.2 - 8.4 | (1 year and 4 months ago) | Active | 5.6.4 (3 days ago) |
Kirby Releases Nearing End of Life - Support Ending Soon (1)
| Release | Supported Php Versions | Released | Security Support | Latest |
|---|---|---|---|---|
| 4 (A new era) | 8.1 - 8.4 | (2 years and 11 months ago) | (in 1 week) | 4.9.8 (5 days ago) |
Kirby End of Life (EOL) Releases - No Longer Supported (19)
| Release | Supported Php Versions | Released | Security Support | Latest |
|---|---|---|---|---|
| 3.10 | 8.1 - 8.3 | (2 years and 11 months ago) | (11 months ago) | 3.10.1.2 (1 year and 6 months ago) |
| 3.9 (Brookesia) | 8.0 - 8.2 | (3 years and 10 months ago) | (11 months ago) | 3.9.8.3 (1 year and 6 months ago) |
| 3.8 (Rhampholeon) | 8.0 - 8.1 | (4 years and 1 month ago) | (1 year and 10 months ago) | 3.8.4.4 (2 years and 2 months ago) |
| 3.7 (Kinyongia) | 7.4 - 8.1 | (4 years and 4 months ago) | (2 years and 1 month ago) | 3.7.5.5 (2 years and 2 months ago) |
| 3.6 (Jungle Calumma) | 7.4 - 8.1 | (5 years ago) | (2 years and 4 months ago) | 3.6.6.6 (2 years and 2 months ago) |
| 3.5 (Calumma) | 7.3 - 8.0 | (5 years and 11 months ago) | (3 years ago) | 3.5.8.4 (3 years and 3 months ago) |
| 3.4 (Furcifer) | 7.2 - 7.4 | (6 years and 4 months ago) | (5 years ago) | 3.4.5 (5 years and 11 months ago) |
| 3.3 (Trioceros) | 7.1 - 7.4 | (7 years ago) | (5 years ago) | 3.3.6 (6 years and 6 months ago) |
| 3.2 (Archaius) | 7.1 - 7.3 | (7 years and 4 months ago) | (5 years ago) | 3.2.5 (7 years and 1 month ago) |
| 3.1 (Chamaeleo) | 7.1 - 7.3 | (7 years and 8 months ago) | (5 years ago) | 3.1.4 (7 years and 6 months ago) |
| 3.0 | 7.1 - 7.3 | (7 years and 10 months ago) | (5 years ago) | 3.0.3 (7 years and 8 months ago) |
| 2.5 | - | (9 years and 5 months ago) | (5 years and 10 months ago) | 2.5.14 (5 years and 11 months ago) |
| 2.4 | - | (10 years ago) | (5 years and 10 months ago) | 2.4.2 (9 years and 1 month ago) |
| 2.3 | - | (10 years and 6 months ago) | (5 years and 10 months ago) | 2.3.3 (9 years ago) |
| 2.2 | - | (11 years ago) | (5 years and 10 months ago) | 2.2.3 (10 years and 11 months ago) |
| 2.1 | - | (11 years and 6 months ago) | (5 years and 10 months ago) | 2.1.1 (11 years and 3 months ago) |
| 2.0 | - | (12 years and 1 month ago) | (5 years and 10 months ago) | 2.0.6 (11 years and 10 months ago) |
| 1.1 | - | (14 years and 5 months ago) | (10 years and 9 months ago) | 1.1.2 (13 years and 9 months ago) |
| 1.0 | - | (14 years and 10 months ago) | (10 years and 9 months ago) | 1.0.9 (14 years and 7 months ago) |
Kirby end of life is the date your Kirby release stops getting fixes. Kirby is a flat-file content management system written in PHP, and Kirby 5 is the latest version to pick for new projects. Older majors received backported fixes for known vulnerabilities, but every release below Kirby 4 is now unsupported, so check what your site runs today.
Kirby End of Life Dates and Supported Versions
The supported versions below follow the security policy on getkirby.com. The docs archive marks Kirby 3.7 and earlier as releases that reached its end of life and are no longer supported, and the page pairs the table with a calendar view, so the docs and the security policy agree on every date. Each row shows the support status of one release, and the old docs stay online for reference only.
| Kirby CMS version | Support status | Initial release | Feature updates until | Security updates until |
|---|---|---|---|---|
| v5 | Supported | June 24, 2025 | Next major release | June 24, 2028 |
| v4 | Security updates only | November 28, 2023 | June 24, 2025 | November 28, 2026 |
| v3.10 | End of life | December 19, 2023 | December 19, 2023 | December 1, 2025 |
| v3.9 | End of life | January 17, 2023 | November 28, 2023 | December 1, 2025 |
| v3.8 | End of life | October 6, 2022 | January 17, 2023 | December 2, 2024 |
| v3.7 | End of life | June 27, 2022 | October 6, 2022 | June 27, 2024 |
| v3.6 | End of life | November 16, 2021 | June 27, 2022 | June 27, 2024 |
| v3.5 | End of life | December 15, 2020 | November 16, 2021 | November 16, 2023 |
| v2 | End of life | October 7, 2014 | February 5, 2019 | January 1, 2021 |
| v1 | End of life | January 9, 2012 | October 7, 2014 | February 1, 2016 |
Security updates for Kirby 4 until November 2026
Kirby 4 receives security updates only, and that security support ends on November 28, 2026. Feature updates stopped on June 24, 2025, when Kirby 5 shipped, so treat the timeline as a countdown to an upgrade.
Latest version and the major release cycle
Kirby 5.6.2 is the newest Kirby release. Since Kirby 4 the project follows semantic versioning, so each major release gets feature updates until the next one ships and security fixes for about three years. A minor version stays supported for two more years after the next minor arrives. Developers can read the changelog on each Kirby CMS release page, and the security policy lists a machine-readable JSON copy of the table, which suits an API-driven monitoring check.
What an Unsupported Kirby CMS Release Means
An unsupported release does not switch your site off. The vendor simply stops shipping compatibility updates and technical support, so every update after support ended is yours to write. Meanwhile each browser, hosting stack and third-party integration keeps moving. Each release also targets a PHP range, such as PHP 8.2 to 8.4 for Kirby 5, so an out of support release gradually loses its place on the platform you deploy to. Your plugin dependencies age with it, and developers then carry every fix alone, and an end-of-life CMS is only maintained by your own team. Kirby is a lean CMS, so the vendor here is a small team that backs the latest major release first.
Support phases: from active support to sunset
Kirby uses three marks: full support, security-only, and sunset, unlike vendors that run a version through mainstream support and extended support before it ends. The support window of each major release shows which phase you are in, and no extended support exists beyond it. If a project needs extended support, treat a migration to a maintained platform as the only paid-for safety net.
What stops: security patches and bug fixes
- Security patches for newly found holes
- Bug fixes for the browsers and PHP versions you run
- Official answers when something breaks
Security Risk of an Out of Support Kirby Version
The real risk is each new vulnerability staying open forever, because attackers scan for unpatched software. The security policy lists every advisory with its CVE and severity, and all fixes below landed only in 4.9.x and 5.x, never in Kirby 3. Its policy page also explains how to report a vulnerability privately, and a critical permission or API flaw is a reason to upgrade quickly.
| Advisory | CVE | Severity | Fixed in |
|---|---|---|---|
| Panel exposed on reverse proxy setups | CVE-2026-54003 | critical (9.1) | 4.9.4, 5.4.4 |
| Pre-authentication path traversal and PHP file inclusion | CVE-2026-44177 | high (8.8) | 5.4.1 |
| Cross-site scripting in Dom::sanitize() | CVE-2026-54002 | high (8.5) | 4.9.4, 5.4.4 |
| Cross-site scripting from list field content | CVE-2026-44175 | high (8.5) | 4.9.1, 5.4.1 |
| Cross-site scripting from KirbyTags links | CVE-2026-45368 | high (8.4) | 4.9.1, 5.4.1 |
| Path traversal in media handling | CVE-2026-75594 | high (8.2) | 4.9.5, 5.5.2 |
| Image access outside the site root via path traversal | CVE-2026-75592 | medium (6.9) | 4.9.5, 5.5.2 |
| Arbitrary method call via REST API search | CVE-2026-44174 | high (8.7) | 4.9.1, 5.4.1 |
| File upload permissions skipped for chunk data | CVE-2026-71415 | high (7.1) | 5.5.2 |
| Drafts files not protected by permissions | CVE-2026-54004 | medium (6.3) | 4.9.4, 5.4.4 |
Compliance and audit exposure
A Kirby 3 site still running after December 2025 has no security updates, which can break internal security rules and fail a customer audit, so compliance becomes a real blocker for agencies selling Kirby sites.
Cost of running production on unpatched code
Every production site left on unsupported Kirby 3 turns each new advisory into an emergency fix on unpatched code, a hidden cost that outweighs a planned move to Kirby 4 or 5.
Sunset Plan: Upgrade Before the Kirby Support Window Closes
Build a sunset plan early instead of a panic fix. Start with an audit of your current Kirby version and PHP release, then set a realistic timeline of six to twelve months before the final security date. That plan keeps the replatform or upgrade in your hands.
Decide between an upgrade and a migration
Moving Kirby 4 to Kirby 5 is an upgrade. Leaving Kirby entirely is a migration, which only makes sense when the site outgrows what the CMS can do. A migration needs content mapping, redirects and testing, so book the migration well before the last security date, and keep the old CMS site as a fallback until the migration is verified.