Kirby 4 · Version Status
Kirby 4 End of Life Date
Kirby 4 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Kirby 4 is actively supported. EOL date: June 23, 2027.
EOL Date
Jun 23, 2027
410 days remaining
Latest Release
4.9.0
Standard release
Release Date
Nov 28, 2023
Kirby 4 series
| Version | Latest | EOL Date | Status |
| 1.0 |
1.0.9 |
Feb 1, 2016 |
EOL |
| 1.1 |
1.1.2 |
Feb 1, 2016 |
EOL |
| 2.0 |
2.0.6 |
Jan 1, 2021 |
EOL |
| 2.1 |
2.1.1 |
Jan 1, 2021 |
EOL |
| 2.2 |
2.2.3 |
Jan 1, 2021 |
EOL |
| 2.3 |
2.3.3 |
Jan 1, 2021 |
EOL |
| 2.4 |
2.4.2 |
Jan 1, 2021 |
EOL |
| 2.5 |
2.5.14 |
Jan 1, 2021 |
EOL |
What does Kirby 4 end of life mean?
When Kirby 4 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Kirby 4 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Kirby 5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Kirby 4 reach end of life?
Kirby 4 reached end of life on June 23, 2027. That is 410 days remaining.
Is Kirby 4 still supported?
Yes, Kirby 4 is currently supported. The EOL date is June 23, 2027.
What should I upgrade to from Kirby 4?
The recommended upgrade from Kirby 4 is
Kirby 5 — the latest actively supported version. Check the
Kirby full timeline for all supported versions.
What are the security risks of running Kirby 4 past EOL?
When Kirby 4 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Kirby should migrate immediately or implement compensating controls.