Complete end-of-life dates, support windows, and security status for all Api Platform versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.0 | 2.0.11 | Nov 24, 2016 | Feb 16, 2018 | 3004 days past EOL | EOL |
| 2.1 | 2.1.6 | Sep 8, 2017 | Jul 6, 2018 | 2864 days past EOL | EOL |
| 2.2 | 2.2.10 | Feb 16, 2018 | Mar 22, 2019 | 2605 days past EOL | EOL |
| 2.3 | 2.3.6 | Jul 6, 2018 | Sep 30, 2019 | 2413 days past EOL | EOL |
| 2.4 | 2.4.7 | Mar 22, 2019 | Jan 22, 2021 | 1933 days past EOL | EOL |
| 2.5 | 2.5.10 | Sep 30, 2019 | Sep 15, 2022 | 1332 days past EOL | EOL |
| 2.6 | 2.6.8 | Jan 22, 2021 | Sep 15, 2022 | 1332 days past EOL | EOL |
| 2.7 | 2.7.18 | Sep 15, 2022 | Jan 27, 2023 | 1198 days past EOL | EOL |
| 3.0 | 3.0.12 | Sep 15, 2022 | Oct 12, 2023 | 940 days past EOL | EOL |
| 3.1 | 3.1.29 | Jan 23, 2023 | Apr 29, 2024 | 740 days past EOL | EOL |
| 3.2 | 3.2.26 | Oct 12, 2023 | Sep 18, 2024 | 598 days past EOL | EOL |
| 3.3 | 3.3.15 | Apr 29, 2024 | Feb 28, 2025 | 435 days past EOL | EOL |
| 3.4 | 3.4.17 | Sep 18, 2024 | Feb 28, 2025 | 435 days past EOL | EOL |
| 4.0 | 4.0.22 | Sep 18, 2024 | Sep 18, 2025 | 233 days past EOL | EOL |
| 4.1 | 4.1.28 | Feb 28, 2025 | Mar 13, 2026 | 57 days past EOL | EOL |
| 4.2 | 4.2.24 | Sep 18, 2025 | Already EOL | Supported | Active |
| 4.3 | 4.3.4 | Mar 13, 2026 | Already EOL | Supported | Active |
When a Api Platform 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 Api Platform 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 →