Logstash End of Life Dates
other
Developers rely on Logstash to process and manage their log data, a crucial task in maintaining the health and security of their applications. Created to solve the problem of log data management, Logstash has been a trusted tool for many years, maintained by the Elastic team. The reason developers use Logstash is its ability to collect, parse, and output log data from various sources, making it an essential component in their data processing pipelines. With its origins dating back to 2010, Logstash has become a staple in the world of log data management.
The end-of-life landscape for Logstash is characterized by a total of 10 versions, with 8 of them already reaching their end-of-life dates. Currently, only 2 versions remain active, with the latest stable version being 9.4.2. Looking ahead, the next version to expire is 8.19, which is scheduled to reach its end-of-life on 2027-07-15. This gives developers ample time to plan their upgrades and ensure a smooth transition to a supported version. The most recent version to reach its end-of-life was 9.3, which expired on 2026-05-08, serving as a reminder to stay up-to-date with the latest versions.
Given the current security landscape, Logstash has a clean slate with 0 tracked CVEs and 0 critical CVEs. As a result, there is no most affected version, and no action is required to address any known vulnerabilities. Additionally, since there are no known vulnerabilities, Logstash is not listed on the Known Exploited Vulnerabilities catalog. This is a testament to the Elastic team's commitment to maintaining the security and integrity of Logstash. Nevertheless, developers should continue to monitor the security patch timelines and plan their upgrades accordingly to ensure they remain on a supported version, such as the latest stable version 9.4.2.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 9.4 | May 8, 2026 | — | No | — | 9.4.4 | — | Active | |
| 9.3 | Feb 3, 2026 | — | May 8, 2026 | 77d ago | 9.3.8 | — | EOL | |
| 9.2 | Oct 21, 2025 | — | Mar 31, 2026 | 115d ago | 9.2.8 | — | EOL | |
| 9.1 | Jul 22, 2025 | — | Jan 7, 2026 | 198d ago | 9.1.10 | — | EOL | |
| 8.19 | Jul 14, 2025 | — | Jul 15, 2027 | in 356d | 8.19.19 | — | Active | |
| 8.18 | Apr 9, 2025 | — | Oct 21, 2025 | 276d ago | 8.18.8 | — | EOL | |
| 9.0 | Mar 17, 2025 | — | Sep 30, 2025 | 297d ago | 9.0.8 | — | EOL | |
| 8.17 | Dec 4, 2024 | — | Aug 6, 2025 | 352d ago | 8.17.10 | — | EOL | |
| 7 | Apr 5, 2019 | — | Jan 15, 2026 | 190d ago | 7.17.29 | — | EOL | |
| 6 | Nov 8, 2017 | — | Feb 10, 2022 | 1625d ago | 6.8.23 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
