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.
Kuma 2.14 is supported until June 12, 2027, its end-of-support date. The next Kuma version to reach end of life is 2.7, on October 19, 2026. 17 of 22 tracked Kuma versions are past end of life; the most recent to reach it, 2.12, did so on September 9, 2026. The full Kuma lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.2 | 1.2.3 | Jun 17, 2021 | Jun 17, 2022 | 1559 days past EOL | EOL |
| 1.3 | 1.3.1 | Aug 24, 2021 | Aug 26, 2022 | 1489 days past EOL | EOL |
| 1.4 | 1.4.1 | Nov 19, 2021 | Nov 22, 2022 | 1401 days past EOL | EOL |
| 1.5 | 1.5.5 | Feb 24, 2022 | Feb 24, 2023 | 1307 days past EOL | EOL |
| 1.6 | 1.6.5 | Apr 11, 2022 | Apr 12, 2023 | 1260 days past EOL | EOL |
| 1.7 | 1.7.6 | Jun 13, 2022 | Jun 16, 2023 | 1195 days past EOL | EOL |
| 1.8 | 1.8.8 | Aug 22, 2022 | Aug 24, 2023 | 1126 days past EOL | EOL |
| 2.0 | 2.0.8 | Nov 4, 2022 | Nov 4, 2023 | 1054 days past EOL | EOL |
| 2.1 | 2.1.7 | Jan 30, 2023 | Feb 1, 2024 | 965 days past EOL | EOL |
| 2.2 | 2.2.9 | Apr 14, 2023 | Apr 14, 2024 | 892 days past EOL | EOL |
| 2.3 | 2.3.7 | Jun 23, 2023 | Jun 23, 2024 | 822 days past EOL | EOL |
| 2.4 | 2.4.10 | Aug 29, 2023 | Aug 29, 2024 | 755 days past EOL | EOL |
| 2.5 | 2.5.11 | Nov 15, 2023 | Nov 15, 2024 | 677 days past EOL | EOL |
| 2.6 | 2.6.15 | Feb 1, 2024 | Feb 1, 2025 | 599 days past EOL | EOL |
| 2.7 LTS | 2.7.30 | Apr 19, 2024 | Oct 19, 2026 | 26 days remaining | Warning |
| 2.8 | 2.8.8 | Jun 24, 2024 | Jun 24, 2025 | 456 days past EOL | EOL |
| 2.9 | 2.9.20 | Oct 22, 2024 | Oct 22, 2026 | 29 days remaining | Warning |
| 2.10 | 2.10.11 | Mar 20, 2025 | Mar 20, 2026 | 187 days past EOL | EOL |
| 2.11 | 2.11.19 | Jun 10, 2025 | Dec 10, 2026 | 78 days remaining | Warning |
| 2.12 | 2.12.15 | Sep 9, 2025 | Sep 9, 2026 | 14 days past EOL | EOL |
| 2.13 | 2.13.11 | Dec 22, 2025 | Dec 22, 2027 | 455 days remaining | Active |
| 2.14 | 2.14.5 | Jun 12, 2026 | Jun 12, 2027 | 262 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/kuma)
Kuma release and support pattern
Across the 22 release lines with a published release date, Kuma has shipped a new line roughly every 3 months (median interval). A line typically stays supported for about 1 year from its release to its end-of-life date. 1 of the 22 tracked lines is designated long-term support, which is where the longer windows sit.
Of the 22 release lines tracked, 17 are past end of life and 5 are still within support. The newest line, 2.14, was released June 12, 2026. The next scheduled end of life is 2.7 on October 19, 2026 — 26 days from this build. The longest-supported line currently published is 2.13, to December 22, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps 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.
Your options when Kuma reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
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.
Kuma has 17 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Kuma is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."