Complete end-of-life dates, support windows, and security status for all Big Ip versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 15.0 | 15.0.1 | May 23, 2019 | Aug 23, 2020 | 2085 days past EOL | EOL |
| 15.1 LTS | 15.1.10 | Dec 11, 2019 | Dec 31, 2025 | 129 days past EOL | EOL |
| 16.0 | 16.0.1.1 | Jul 16, 2020 | Oct 7, 2021 | 1675 days past EOL | EOL |
| 16.1 LTS | 16.1.6 | Jul 7, 2021 | Jul 1, 2026 | 53 days remaining | Warning |
| 17.0 | 17.0.0 | Apr 26, 2022 | Jul 31, 2023 | 1013 days past EOL | EOL |
| 17.1 LTS | 17.1.3 | Mar 14, 2023 | Mar 31, 2027 | 326 days remaining | Active |
| 17.5 LTS | 17.5.1 | Feb 27, 2025 | Jan 1, 2029 | 968 days remaining | Active |
| 21.0 | 21.0.0 | Nov 6, 2025 | Aug 6, 2026 | 89 days remaining | Warning |
When a Big Ip 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 Big Ip 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 →