Icinga Web · Lifecycle Status

Icinga Web End of Life (EOL) Dates & Support Timeline

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.

Icinga Web 2.12.6 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
2.12.6
2.12 series
Next EOL
None upcoming
Active Versions
2
of 15 total
EOL Versions
13
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 201120122013201420152016201720182019202020212022202320242025202612.02.12.22.32.42.52.62.72.82.92.102.112.122.13TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
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

What does Icinga Web end of life mean for your organization?

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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Icinga Web?
See the full table above for all Icinga Web version EOL dates.
What is the latest supported version of Icinga Web?
The latest active version of Icinga Web is 2.12.6. Always verify against the table above as support windows can change.
What happens when Icinga Web reaches end of life?
When Icinga Web reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Icinga Web?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Icinga Web versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →