Kuma End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Kuma versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.2 | 1.2.3 | Jun 17, 2021 | Jun 17, 2022 | 1467 days past EOL | EOL |
| 1.3 | 1.3.1 | Aug 24, 2021 | Aug 26, 2022 | 1397 days past EOL | EOL |
| 1.4 | 1.4.1 | Nov 19, 2021 | Nov 22, 2022 | 1309 days past EOL | EOL |
| 1.5 | 1.5.5 | Feb 24, 2022 | Feb 24, 2023 | 1215 days past EOL | EOL |
| 1.6 | 1.6.5 | Apr 11, 2022 | Apr 12, 2023 | 1168 days past EOL | EOL |
| 1.7 | 1.7.6 | Jun 13, 2022 | Jun 16, 2023 | 1103 days past EOL | EOL |
| 1.8 | 1.8.8 | Aug 22, 2022 | Aug 24, 2023 | 1034 days past EOL | EOL |
| 2.0 | 2.0.8 | Nov 4, 2022 | Nov 4, 2023 | 962 days past EOL | EOL |
| 2.1 | 2.1.7 | Jan 30, 2023 | Feb 1, 2024 | 873 days past EOL | EOL |
| 2.2 | 2.2.9 | Apr 14, 2023 | Apr 14, 2024 | 800 days past EOL | EOL |
| 2.3 | 2.3.7 | Jun 23, 2023 | Jun 23, 2024 | 730 days past EOL | EOL |
| 2.4 | 2.4.10 | Aug 29, 2023 | Aug 29, 2024 | 663 days past EOL | EOL |
| 2.5 | 2.5.11 | Nov 15, 2023 | Nov 15, 2024 | 585 days past EOL | EOL |
| 2.6 | 2.6.15 | Feb 1, 2024 | Feb 1, 2025 | 507 days past EOL | EOL |
| 2.7 LTS | 2.7.27 | Apr 19, 2024 | Oct 19, 2026 | 118 days remaining | Warning |
| 2.8 | 2.8.8 | Jun 24, 2024 | Jun 24, 2025 | 364 days past EOL | EOL |
| 2.9 | 2.9.17 | Oct 22, 2024 | Jun 22, 2026 | 1 days past EOL | EOL |
| 2.10 | 2.10.11 | Mar 20, 2025 | Mar 20, 2026 | 95 days past EOL | EOL |
| 2.11 | 2.11.15 | Jun 10, 2025 | Dec 10, 2026 | 170 days remaining | Warning |
| 2.12 | 2.12.12 | Sep 9, 2025 | Sep 9, 2026 | 78 days remaining | Warning |
| 2.13 | 2.13.8 | Dec 22, 2025 | Dec 22, 2027 | 547 days remaining | Active |
| 2.14 | 2.14.0 | Jun 12, 2026 | Jun 12, 2027 | 354 days remaining | Active |
What does Kuma end of life mean for your organization?
When a version of Kuma 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 Kuma 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 Kuma 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 →