PHP End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all PHP versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5.0 | 5.0.5 | Jul 13, 2004 | Sep 5, 2005 | 7596 days past EOL | EOL |
| 5.1 | 5.1.6 | Nov 24, 2005 | Aug 24, 2006 | 7243 days past EOL | EOL |
| 5.2 | 5.2.17 | Nov 2, 2006 | Jan 6, 2011 | 5647 days past EOL | EOL |
| 5.3 | 5.3.29 | Jun 30, 2009 | Aug 14, 2014 | 4331 days past EOL | EOL |
| 5.4 | 5.4.45 | Mar 1, 2012 | Sep 14, 2015 | 3935 days past EOL | EOL |
| 5.5 | 5.5.38 | Jun 20, 2013 | Jul 21, 2016 | 3624 days past EOL | EOL |
| 5.6 | 5.6.40 | Aug 28, 2014 | Dec 31, 2018 | 2731 days past EOL | EOL |
| 7.0 | 7.0.33 | Dec 3, 2015 | Jan 10, 2019 | 2721 days past EOL | EOL |
| 7.1 | 7.1.33 | Dec 1, 2016 | Dec 1, 2019 | 2396 days past EOL | EOL |
| 7.2 | 7.2.34 | Nov 30, 2017 | Nov 30, 2020 | 2031 days past EOL | EOL |
| 7.3 | 7.3.33 | Dec 6, 2018 | Dec 6, 2021 | 1660 days past EOL | EOL |
| 7.4 | 7.4.33 | Nov 28, 2019 | Nov 28, 2022 | 1303 days past EOL | EOL |
| 8.0 | 8.0.30 | Nov 26, 2020 | Nov 26, 2023 | 940 days past EOL | EOL |
| 8.1 | 8.1.34 | Nov 25, 2021 | Dec 31, 2025 | 174 days past EOL | EOL |
| 8.2 | 8.2.31 | Dec 8, 2022 | Dec 31, 2026 | 191 days remaining | Active |
| 8.3 | 8.3.31 | Nov 23, 2023 | Dec 31, 2027 | 556 days remaining | Active |
| 8.4 | 8.4.22 | Nov 21, 2024 | Dec 31, 2028 | 922 days remaining | Active |
| 8.5 | 8.5.7 | Nov 20, 2025 | Dec 31, 2029 | 1287 days remaining | Active |
What does PHP end of life mean for your organization?
When a version of PHP 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 PHP 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL PHP versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →