Kuma 2.13 · Version Status
Kuma 2.13 End of Life Date
Kuma 2.13 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Kuma 2.13 is actively supported. EOL date: December 22, 2027.
EOL Date
Dec 22, 2027
592 days remaining
Latest Release
2.13.5
Standard release
Release Date
Dec 22, 2025
Kuma 2.13 series
| Version | Latest | EOL Date | Status |
|---|
| 1.2 |
1.2.3 |
Jun 17, 2022 |
EOL |
| 1.3 |
1.3.1 |
Aug 26, 2022 |
EOL |
| 1.4 |
1.4.1 |
Nov 22, 2022 |
EOL |
| 1.5 |
1.5.5 |
Feb 24, 2023 |
EOL |
| 1.6 |
1.6.5 |
Apr 12, 2023 |
EOL |
| 1.7 |
1.7.6 |
Jun 16, 2023 |
EOL |
| 1.8 |
1.8.8 |
Aug 24, 2023 |
EOL |
| 2.0 |
2.0.8 |
Nov 4, 2023 |
EOL |
What does Kuma 2.13 end of life mean?
When Kuma 2.13 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 Kuma 2.13 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Kuma 2.13 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Kuma 2.13 reach end of life?
Kuma 2.13 reached end of life on December 22, 2027. That is 592 days remaining.
Is Kuma 2.13 still supported?
Yes, Kuma 2.13 is currently supported. The EOL date is December 22, 2027.
What should I upgrade to from Kuma 2.13?
The recommended upgrade from Kuma 2.13 is
Kuma 2.13 — the latest actively supported version. Check the
Kuma full timeline for all supported versions.
What are the security risks of running Kuma 2.13 past EOL?
When Kuma 2.13 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 Kuma should migrate immediately or implement compensating controls.