Complete end-of-life dates, support windows, and security status for all Beats versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 6 | 6.8.23 | Nov 8, 2017 | Feb 10, 2022 | 1549 days past EOL | EOL |
| 7 | 7.17.29 | Apr 5, 2019 | Jan 15, 2026 | 114 days past EOL | EOL |
| 8.16 | 8.16.6 | Nov 7, 2024 | Apr 18, 2025 | 386 days past EOL | EOL |
| 8.17 | 8.17.10 | Dec 11, 2024 | Already EOL | Supported | Active |
| 9.0 | 9.0.8 | Apr 8, 2025 | Already EOL | Supported | Active |
| 8.18 | 8.18.8 | Apr 9, 2025 | Oct 20, 2025 | 201 days past EOL | EOL |
| 8.19 | 8.19.15 | Jul 23, 2025 | Jul 15, 2027 | 432 days remaining | Active |
| 9.1 | 9.1.10 | Jul 23, 2025 | Already EOL | Supported | Active |
| 9.2 | 9.2.8 | Oct 20, 2025 | Already EOL | Supported | Active |
| 9.3 | 9.3.4 | Feb 3, 2026 | Already EOL | Supported | Active |
When a Beats version 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: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Beats 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →