Complete end-of-life dates, support windows, and security status for all Laravel versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5.5 LTS | 5.5.50 | Aug 30, 2017 | Aug 30, 2020 | 2078 days past EOL | EOL |
| 5.8 | 5.8.38 | Feb 26, 2019 | Feb 26, 2020 | 2264 days past EOL | EOL |
| 6 LTS | 6.20.45 | Sep 3, 2019 | Sep 6, 2022 | 1341 days past EOL | EOL |
| 7 | 7.30.7 | Mar 3, 2020 | Mar 3, 2021 | 1893 days past EOL | EOL |
| 8 | 8.83.29 | Sep 8, 2020 | Jan 24, 2023 | 1201 days past EOL | EOL |
| 9 | 9.52.21 | Feb 8, 2022 | Feb 6, 2024 | 823 days past EOL | EOL |
| 10 | 10.50.2 | Feb 14, 2023 | Feb 4, 2025 | 459 days past EOL | EOL |
| 11 | 11.51.0 | Mar 12, 2024 | Mar 12, 2026 | 58 days past EOL | EOL |
| 12 | 12.58.0 | Feb 24, 2025 | Feb 24, 2027 | 291 days remaining | Active |
| 13 | 13.8.0 | Mar 17, 2026 | Mar 17, 2028 | 678 days remaining | Active |
When a Laravel 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 Laravel 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 →