iOS End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all iOS versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5 | 5.1.1 | Oct 12, 2011 | Nov 1, 2012 | 5002 days past EOL | EOL |
| 6 | 6.1.6 | Sep 19, 2012 | Sep 26, 2013 | 4673 days past EOL | EOL |
| 7 | 7.1.2 | Sep 18, 2013 | Oct 20, 2014 | 4284 days past EOL | EOL |
| 8 | 8.4.1 | Sep 17, 2014 | Sep 30, 2015 | 3939 days past EOL | EOL |
| 9 | 9.3.6 | Sep 16, 2015 | Jul 22, 2019 | 2548 days past EOL | EOL |
| 10 | 10.3.4 | Sep 13, 2016 | Jul 22, 2019 | 2548 days past EOL | EOL |
| 11 | 11.4.1 | Sep 19, 2017 | Oct 8, 2018 | 2835 days past EOL | EOL |
| 12 | 12.5.8 | Sep 17, 2018 | Jan 26, 2026 | 168 days past EOL | EOL |
| 13 | 13.7 | Sep 19, 2019 | Sep 16, 2020 | 2126 days past EOL | EOL |
| 14 | 14.8.1 | Sep 16, 2020 | Oct 26, 2021 | 1721 days past EOL | EOL |
| 15 | 15.8.8 | Sep 20, 2021 | TBD | Supported | Active |
| 16 | 16.7.16 | Sep 12, 2022 | TBD | Supported | Active |
| 17 | 17.7.2 | Sep 18, 2023 | Nov 19, 2024 | 601 days past EOL | EOL |
| 18 | 18.7.9 | Sep 16, 2024 | TBD | Supported | Active |
| 26 | 26.5.2 | Sep 15, 2025 | TBD | Supported | Active |
What does iOS end of life mean for your organization?
When a version of iOS 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 iOS 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 →