PHP, Laravel and MySQL end-of-life dates
Bug fixes end first; security fixes end later; after that a version receives nothing. Status is computed from the dates on the day you read this page. The tables are plain HTML so you — or an assistant — can cite them.
Last verified: . Sources: PHP supported versions · Laravel support policy · MySQL lifetime support policy · endoflife.date
Security windows closing in the next 400 days
- PHP 8.2 — 31 December 2026 (97 days)
- Laravel 12 — 24 February 2027 (152 days)
PHP versions
Each PHP release gets two years of active support (bug fixes) and then two more years of security fixes — four years total since PHP 8.1.
| PHP version | Bug fixes until | Security fixes until | Status today |
|---|---|---|---|
| 8.5 | 31 December 2027 | 31 December 2029 | Supported |
| 8.4 | 31 December 2026 | 31 December 2028 | Supported |
| 8.3Minimum for Laravel 13 | 31 December 2025 | 31 December 2027 | Security fixes only |
| 8.2Minimum for Laravel 11 and 12 | 31 December 2024 | 31 December 2026in 97 days | Security fixes only |
| 8.1 | 25 November 2023 | 31 December 2025 | Unsupported |
| 8.0 | 26 November 2022 | 26 November 2023 | Unsupported |
| 7.4 | 28 November 2021 | 28 November 2022 | Unsupported |
| 7.3 | 6 December 2020 | 6 December 2021 | Unsupported |
| 7.2 | 30 November 2019 | 30 November 2020 | Unsupported |
| 7.1 | 1 December 2018 | 1 December 2019 | Unsupported |
| 7.0 | 4 January 2018 | 10 January 2019 | Unsupported |
| 5.6 | 19 January 2017 | 31 December 2018 | Unsupported |
Laravel versions
Since Laravel 8: 18 months of bug fixes, 24 months of security fixes, a new major each first quarter, and no LTS releases. Laravel 6 (September 2019) was the last LTS.
| Laravel version | Bug fixes until | Security fixes until | Status today |
|---|---|---|---|
| 13Requires PHP 8.3+ | 30 September 2027 | 17 March 2028 | Supported |
| 12Requires PHP 8.2+ | 13 August 2026 | 24 February 2027in 152 days | Security fixes only |
| 11Requires PHP 8.2+ | 3 September 2025 | 12 March 2026 | Unsupported |
| 10Requires PHP 8.1+ | 6 August 2024 | 4 February 2025 | Unsupported |
| 9Requires PHP 8.0+ | 8 August 2023 | 6 February 2024 | Unsupported |
| 8Requires PHP 7.3+ | 26 July 2022 | 24 January 2023 | Unsupported |
| 7Requires PHP 7.2.5+ | 6 October 2020 | 3 March 2021 | Unsupported |
| 6LTS · requires PHP 7.2+ | 25 January 2022 | 6 September 2022 | Unsupported |
| 5.8Requires PHP 7.1.3+ | 26 August 2019 | 26 February 2020 | Unsupported |
| 5.5LTS · requires PHP 7.0+ | 30 August 2019 | 30 August 2020 | Unsupported |
MySQL versions
MySQL 5.7 ended in October 2023 and 8.0 in April 2026. MySQL 8.4 is the long-term-support target; the 9.x innovation releases are superseded every quarter.
| MySQL version | Bug fixes until | Security fixes until | Status today |
|---|---|---|---|
| 9.7Innovation track | 21 April 2029 | 21 April 2034 | Supported |
| 8.4LTS — recommended target | 30 April 2029 | 30 April 2032 | Supported |
| 8.0 | 30 April 2025 | 30 April 2026 | Unsupported |
| 5.7 | 31 October 2020 | 31 October 2023 | Unsupported |
| 5.6 | 28 February 2018 | 28 February 2021 | Unsupported |
Last verified: against php.net, laravel.com and endoflife.date. Full end-of-life calendar →
Reading the two dates
- Bug fixes until
- The end of “active support”. Until this date, ordinary bugs are fixed in point releases. After it, only security issues are.
- Security fixes until
- The end of life. After this date a vulnerability found in the runtime or framework is never patched for that version. Insurers, auditors and hosts use this date.
- Laravel’s cadence
- One major per year in Q1; each supported for 18 months (bugs) and 24 months (security). Staying current means one hop a year, which is what a care plan schedules.
What to do if you’re on an unsupported version
- 01Find out exactly what you run — the version note below reads it from your site’s public signals.
- 02Read the guide for your starting version: what’s exposed, the hop order, what breaks.
- 03Get a fixed price with a read-only Assessment (3–5 working days, credited if you proceed).
Not sure which versions you run?
Send the URL. We read the public signals your site sends — headers, cookies, asset paths — and email the versions with their dates. No access needed.
Questions about end of life
What does end of life mean for a PHP or Laravel version?
No more releases. For PHP, 'active support' means bug fixes and 'security support' means security-only fixes; after the security date, known vulnerabilities are never patched. Laravel majors get 18 months of bug fixes and 24 months of security fixes from release.
Does Laravel have an LTS version?
Not any more. Laravel 6 (September 2019) was the last LTS. Since Laravel 8, every major gets the same 18/24-month window and a new major ships each first quarter, so staying current means one hop a year.
Is running an unsupported version illegal or a compliance failure?
It is not illegal, but it is a finding in most security questionnaires. Cyber-insurance forms, SOC 2 reviews and customer security assessments ask for supported runtimes, and hosts increasingly drop old PHP builds. The practical risk is unpatched vulnerabilities in the runtime and framework.
How often is this page updated?
The dates come from one data file that we check against php.net, laravel.com and endoflife.date each quarter; the 'last verified' date above the tables is the day of the last check.
Start with a written Assessment.
3–5 working days. A fixed price for the upgrade, a list of what could break, and how we'll prevent it.