Complete end-of-life dates, support windows, and security status for all Idl versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 8.3 | 8.3.0 | Dec 16, 2013 | Jul 1, 2016 | 3599 days past EOL | EOL |
| 8.4 | 8.4.0 | Sep 22, 2014 | Jul 1, 2017 | 3234 days past EOL | EOL |
| 8.5 | 8.5.0 | Jul 10, 2015 | Jul 1, 2018 | 2869 days past EOL | EOL |
| 8.6 | 8.6.0 | Dec 6, 2016 | Jul 1, 2019 | 2504 days past EOL | EOL |
| 8.7 | 8.7.3 | Feb 19, 2018 | Jun 29, 2020 | 2140 days past EOL | EOL |
| 8.8 | 8.8.3 | Jun 29, 2020 | May 3, 2023 | 1102 days past EOL | EOL |
| 8.9 | 8.9.0 | May 3, 2023 | Jul 1, 2023 | 1043 days past EOL | EOL |
| 9.0 | 9.0.0 | Jul 1, 2023 | Sep 25, 2024 | 591 days past EOL | EOL |
| 9.1 | 9.1.0 | Sep 25, 2024 | Aug 15, 2025 | 267 days past EOL | EOL |
| 9.2 | 9.2.0 | Aug 15, 2025 | Already EOL | Supported | Active |
When a Idl 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 Idl 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 →