Kirby 1.0 · Version Status
Kirby 1.0 End of Life Date
Kirby 1.0 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Kirby 1.0 is past end of life. This version no longer receives security patches. 3909 days past EOL — migrate to a supported version immediately.
EOL Date
Feb 1, 2016
3909 days past EOL
Latest Release
1.0.9
Standard release
Release Date
Jan 9, 2012
Kirby 1.0 series
Lifecycle detail
Kirby 1.0 was released on January 9, 2012 and support ended on February 1, 2016 — a supported lifespan of 4 years and 1 month, longer than the 2 years and 11 months median for Kirby releases. The last patch it will ever receive is 1.0.9, published April 20, 2012 — 3 years and 10 months before support ended. It has been without security patches for 10 years and 9 months. 16 newer Kirby releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Kirby 1.0 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| 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 1.0 end of life mean?
When Kirby 1.0 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Kirby 1.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Kirby 5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Kirby 1.0 reach end of life?
Kirby 1.0 reached end of life on February 1, 2016. This version is no longer receiving security patches.
Is Kirby 1.0 still supported?
No. Kirby 1.0 reached end of life on February 1, 2016 and is no longer receiving security patches.
What should I upgrade to from Kirby 1.0?
The recommended upgrade from Kirby 1.0 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 1.0 past EOL?
When Kirby 1.0 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Kirby should migrate immediately or implement compensating controls.