Icinga Web 1 · Version Status
Icinga Web 1 End of Life Date
Icinga Web 1 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Icinga Web 1 is past end of life. This version no longer receives security patches. 2868 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 31, 2018
2868 days past EOL
Latest Release
1.14.1
Standard release
Release Date
Jun 30, 2010
Icinga Web 1 series
Where these dates come from
End of lifeDec 31, 2018endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of active supportOct 2, 2015endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseJun 30, 2010endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Icinga Web 1 was released on June 30, 2010 and support ended on December 31, 2018 — a supported lifespan of 8 years and 6 months, longer than the 1 year and 6 months median for Icinga Web releases. Its latest release on record is 1.14.1, published December 19, 2017 — 1 year before support ended. It has been past its end-of-life date for 7 years and 10 months. 8 newer Icinga Web releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Icinga Web 1 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| → 1 |
1.14.1 |
Dec 31, 2018 |
EOL |
| 2.0 |
2.0.0 |
Nov 16, 2015 |
EOL |
| 2.1 |
2.1.4 |
Feb 29, 2016 |
EOL |
| 2.2 |
2.2.2 |
Apr 13, 2016 |
EOL |
| 2.3 |
2.3.4 |
Dec 13, 2016 |
EOL |
| 2.4 |
2.4.2 |
Nov 27, 2017 |
EOL |
| 2.5 |
2.5.3 |
Jul 19, 2018 |
EOL |
| 2.6 |
2.6.4 |
Jun 8, 2020 |
EOL |
What does Icinga Web 1 end of life mean?
When Icinga Web 1 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Icinga Web 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Icinga Web 2.14 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Icinga Web 1 reach end of life?
Icinga Web 1 reached end of life on December 31, 2018. This version is no longer receiving security patches.
Is Icinga Web 1 still supported?
No. Icinga Web 1 reached end of life on December 31, 2018 and is no longer receiving security patches.
What should I upgrade to from Icinga Web 1?
The recommended upgrade from Icinga Web 1 is
Icinga Web 2.14 — the latest actively supported version. Check the
Icinga Web full timeline for all supported versions.
What are the security risks of running Icinga Web 1 past EOL?
Since Icinga Web 1 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Icinga Web should migrate immediately or implement compensating controls.