Complete end-of-life dates, support windows, and security status for all Icinga Web 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.1 | Jun 30, 2010 | Dec 31, 2018 | 2686 days past EOL | EOL |
| 2.0 | 2.0.0 | Oct 2, 2015 | Nov 16, 2015 | 3827 days past EOL | EOL |
| 2.1 | 2.1.4 | Nov 16, 2015 | Feb 29, 2016 | 3722 days past EOL | EOL |
| 2.2 | 2.2.2 | Feb 29, 2016 | Apr 13, 2016 | 3678 days past EOL | EOL |
| 2.3 | 2.3.4 | Apr 13, 2016 | Dec 13, 2016 | 3434 days past EOL | EOL |
| 2.4 | 2.4.2 | Dec 13, 2016 | Nov 27, 2017 | 3085 days past EOL | EOL |
| 2.5 | 2.5.3 | Nov 27, 2017 | Jul 19, 2018 | 2851 days past EOL | EOL |
| 2.6 | 2.6.4 | Jul 19, 2018 | Jun 8, 2020 | 2161 days past EOL | EOL |
| 2.7 | 2.7.6 | Jul 30, 2019 | Jul 12, 2021 | 1762 days past EOL | EOL |
| 2.8 | 2.8.6 | Jun 8, 2020 | Mar 23, 2022 | 1508 days past EOL | EOL |
| 2.9 | 2.9.9 | Jul 12, 2021 | Jun 30, 2022 | 1409 days past EOL | EOL |
| 2.10 | 2.10.5 | Mar 23, 2022 | Sep 21, 2023 | 961 days past EOL | EOL |
| 2.11 | 2.11.6 | Jun 30, 2022 | Mar 27, 2026 | 43 days past EOL | EOL |
| 2.12 | 2.12.6 | Sep 21, 2023 | Already EOL | Supported | Active |
| 2.13 | 2.13.0 | Mar 27, 2026 | Already EOL | Supported | Active |
When a Icinga Web 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 Web 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 →