Laravel End of Life Dates
framework
Developers working with the popular PHP framework, Laravel, need to stay on top of its lifecycle to ensure their applications remain secure and supported. Created by Taylor Otwell in 2011, Laravel is maintained by him and a team of contributors, providing a robust set of tools for building web applications quickly. The framework's simplicity, elegance, and ease of use have made it a favorite among developers, who rely on it to build scalable and maintainable applications. By tracking Laravel's end-of-life dates, supported versions, and security patch timelines, developers can plan their upgrades and migrations, avoiding potential security risks and compatibility issues.
The Laravel framework has a total of 10 versions, out of which 8 have already reached their end-of-life, while 2 remain actively supported. The latest stable version, 13.15.0, is the current benchmark for new projects and upgrades. However, developers should be aware that version 12 is slated to reach its end-of-life on 2027-02-24, marking an important deadline for migration to a newer version. The most recent end-of-life date was 2026-03-12, when version 11 ceased to receive support, underscoring the need for ongoing vigilance in maintaining up-to-date systems.
Given the current security landscape, Laravel has a clean slate with 0 tracked CVEs and 0 critical vulnerabilities, making it an attractive choice for developers prioritizing security. With no most affected version due to the absence of CVEs, the focus shifts to keeping pace with the framework's evolution. Despite this positive security picture, developers should remain proactive, planning upgrades to the latest stable version, 13.15.0, to leverage the latest features and security enhancements. By doing so, they can ensure their applications remain secure, supported, and aligned with the framework's ongoing development and maintenance efforts.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 13 | Mar 17, 2026 | Sep 30, 2027 | Mar 17, 2028 | in 602d | 13.21.1 | — | Active | |
| 12 | Feb 24, 2025 | Aug 16, 2026 | Feb 24, 2027 | in 215d | 12.64.0 | — | Active | |
| 11 | Mar 12, 2024 | Sep 3, 2025 | Mar 12, 2026 | 134d ago | 11.55.0 | — | EOL | |
| 10 | Feb 14, 2023 | Aug 6, 2024 | Feb 4, 2025 | 535d ago | 10.50.2 | — | EOL | |
| 9 | Feb 8, 2022 | Aug 8, 2023 | Feb 6, 2024 | 899d ago | 9.52.21 | — | EOL | |
| 8 | Sep 8, 2020 | Jul 26, 2022 | Jan 24, 2023 | 1277d ago | 8.83.29 | — | EOL | |
| 7 | Mar 3, 2020 | Oct 6, 2020 | Mar 3, 2021 | 1969d ago | 7.30.7 | — | EOL | |
| 6 LTS | Sep 3, 2019 | Jan 25, 2022 | Sep 6, 2022 | 1417d ago | 6.20.45 | — | EOL | |
| 5.8 | Feb 26, 2019 | Aug 26, 2019 | Feb 26, 2020 | 2340d ago | 5.8.38 | — | EOL | |
| 5.5 LTS | Aug 30, 2017 | Aug 30, 2019 | Aug 30, 2020 | 2154d ago | 5.5.50 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
