Complete end-of-life dates, support windows, and security status for all Icinga versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.14.2 | Dec 15, 2009 | Dec 31, 2018 | 2686 days past EOL | EOL |
| 2.0 | 2.0.2 | Jun 16, 2014 | Aug 29, 2014 | 4271 days past EOL | EOL |
| 2.1 | 2.1.1 | Aug 29, 2014 | Nov 17, 2014 | 4191 days past EOL | EOL |
| 2.2 | 2.2.4 | Nov 17, 2014 | Mar 9, 2015 | 4079 days past EOL | EOL |
| 2.3 | 2.3.11 | Mar 9, 2015 | Nov 16, 2015 | 3827 days past EOL | EOL |
| 2.4 | 2.4.10 | Nov 16, 2015 | Aug 22, 2016 | 3547 days past EOL | EOL |
| 2.5 | 2.5.4 | Aug 22, 2016 | Dec 13, 2016 | 3434 days past EOL | EOL |
| 2.6 | 2.6.3 | Dec 13, 2016 | Aug 2, 2017 | 3202 days past EOL | EOL |
| 2.7 | 2.7.2 | Aug 2, 2017 | Nov 16, 2017 | 3096 days past EOL | EOL |
| 2.8 | 2.8.4 | Nov 16, 2017 | Jul 17, 2018 | 2853 days past EOL | EOL |
| 2.9 | 2.9.3 | Jul 17, 2018 | Oct 11, 2018 | 2767 days past EOL | EOL |
| 2.10 | 2.12.10 | Oct 11, 2018 | Aug 3, 2020 | 2105 days past EOL | EOL |
| 2.11 | 2.11.12 | Sep 19, 2019 | Aug 2, 2021 | 1741 days past EOL | EOL |
| 2.12 | 2.12.12 | Aug 3, 2020 | Jul 12, 2023 | 1032 days past EOL | EOL |
| 2.13 | 2.13.14 | Aug 2, 2021 | Jun 17, 2025 | 326 days past EOL | EOL |
| 2.14 | 2.14.8 | Jul 12, 2023 | Apr 23, 2026 | 16 days past EOL | EOL |
| 2.15 | 2.15.3 | Jun 17, 2025 | Already EOL | Supported | Active |
| 2.16 | 2.16.0 | Apr 23, 2026 | Already EOL | Supported | Active |
When a Icinga 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 Icinga 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 →