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 | 7551 days past EOL | EOL |
| 5.1 | 5.1.6 | Nov 24, 2005 | Aug 24, 2006 | 7198 days past EOL | EOL |
| 5.2 | 5.2.17 | Nov 2, 2006 | Jan 6, 2011 | 5602 days past EOL | EOL |
| 5.3 | 5.3.29 | Jun 30, 2009 | Aug 14, 2014 | 4286 days past EOL | EOL |
| 5.4 | 5.4.45 | Mar 1, 2012 | Sep 14, 2015 | 3890 days past EOL | EOL |
| 5.5 | 5.5.38 | Jun 20, 2013 | Jul 21, 2016 | 3579 days past EOL | EOL |
| 5.6 | 5.6.40 | Aug 28, 2014 | Dec 31, 2018 | 2686 days past EOL | EOL |
| 7.0 | 7.0.33 | Dec 3, 2015 | Jan 10, 2019 | 2676 days past EOL | EOL |
| 7.1 | 7.1.33 | Dec 1, 2016 | Dec 1, 2019 | 2351 days past EOL | EOL |
| 7.2 | 7.2.34 | Nov 30, 2017 | Nov 30, 2020 | 1986 days past EOL | EOL |
| 7.3 | 7.3.33 | Dec 6, 2018 | Dec 6, 2021 | 1615 days past EOL | EOL |
| 7.4 | 7.4.33 | Nov 28, 2019 | Nov 28, 2022 | 1258 days past EOL | EOL |
| 8.0 | 8.0.30 | Nov 26, 2020 | Nov 26, 2023 | 895 days past EOL | EOL |
| 8.1 | 8.1.34 | Nov 25, 2021 | Dec 31, 2025 | 129 days past EOL | EOL |
| 8.2 | 8.2.31 | Dec 8, 2022 | Dec 31, 2026 | 236 days remaining | Active |
| 8.3 | 8.3.31 | Nov 23, 2023 | Dec 31, 2027 | 601 days remaining | Active |
| 8.4 | 8.4.21 | Nov 21, 2024 | Dec 31, 2028 | 967 days remaining | Active |
| 8.5 | 8.5.6 | Nov 20, 2025 | Dec 31, 2029 | 1332 days remaining | Active |
When a Php 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 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.
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.
Extended PHP support beyond official EOL — keep production apps secure.
Learn More →Upload your dependency file and scan your entire stack for EOL risk in seconds. Free, no account required.
Stack Scanner →