Kuma 3.0 · Version Status
Kuma 3.0 End of Life Date
Kuma 3.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.
✓
Kuma 3.0 is actively supported. EOL date: October 15, 2027.
📅 Get reminded before Kuma 3.0 reaches EOL on October 15, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Oct 15, 2027
361 days remaining
Latest Release
3.0.0
Standard release
Release Date
Oct 15, 2026
Kuma 3.0 series
Where these dates come from
End of lifeOct 15, 2027endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseOct 15, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Kuma 3.0 was released on October 15, 2026 and support is scheduled to end on October 15, 2027 — a planned supported lifespan of 1 year, in line with the 1 year median for Kuma releases. It is not an LTS release; Kuma reserves longer patch windows for its LTS versions. Its most recent patch is 3.0.0, published October 15, 2026.
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 →
| 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 3.0 end of life mean?
When Kuma 3.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 Kuma 3.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Kuma 3.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Kuma 3.0 reach end of life?
Kuma 3.0 reaches end of life on October 15, 2027. That is 361 days remaining.
Is Kuma 3.0 still supported?
Yes, Kuma 3.0 is currently supported. The EOL date is October 15, 2027.
What should I upgrade to from Kuma 3.0?
The recommended upgrade from Kuma 3.0 is
Kuma 3.0 — the latest actively supported version. Check the
Kuma full timeline for all supported versions.
What are the security risks of running Kuma 3.0 past EOL?
When Kuma 3.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 Kuma should migrate immediately or implement compensating controls.