Keda 2.7 · Version Status
Keda 2.7 End of Life Date
Keda 2.7 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Keda 2.7 is past end of life. This version no longer receives security patches. 1247 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 9, 2022
1247 days past EOL
Latest Release
2.7.1
Standard release
Release Date
May 5, 2022
Keda 2.7 series
| Version | Latest | EOL Date | Status |
|---|
| 1.5 |
1.5.0 |
Supported |
Active |
| 2.0 |
2.0.0 |
Mar 18, 2021 |
EOL |
| 2.1 |
2.1.0 |
May 27, 2021 |
EOL |
| 2.2 |
2.2.0 |
Aug 6, 2021 |
EOL |
| 2.3 |
2.3.0 |
Nov 25, 2021 |
EOL |
| 2.4 |
2.4.0 |
Jan 31, 2022 |
EOL |
| 2.5 |
2.5.0 |
May 5, 2022 |
EOL |
| 2.6 |
2.6.1 |
Aug 10, 2022 |
EOL |
What does Keda 2.7 end of life mean?
When Keda 2.7 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 Keda 2.7 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Keda 2.19 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Keda 2.7 reach end of life?
Keda 2.7 reached end of life on December 9, 2022. This version is no longer receiving security patches.
Is Keda 2.7 still supported?
No. Keda 2.7 reached end of life on December 9, 2022 and is no longer receiving security patches.
What should I upgrade to from Keda 2.7?
The recommended upgrade from Keda 2.7 is
Keda 2.19 — the latest actively supported version. Check the
Keda full timeline for all supported versions.
What are the security risks of running Keda 2.7 past EOL?
When Keda 2.7 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 Keda should migrate immediately or implement compensating controls.