Laravel 12 · Version Status

Laravel 12 End of Life Date

Laravel 12 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Laravel 12 is actively supported. EOL date: February 24, 2027.
EOL Date
Feb 24, 2027
291 days remaining
Latest Release
12.58.0
Standard release
Release Date
Feb 24, 2025
Laravel 12 series
← Laravel 11 All Laravel versions Laravel 13 →
All Laravel Versions
VersionLatestEOL DateStatus
5.5 LTS 5.5.50 Aug 30, 2020 EOL
5.8 5.8.38 Feb 26, 2020 EOL
6 LTS 6.20.45 Sep 6, 2022 EOL
7 7.30.7 Mar 3, 2021 EOL
8 8.83.29 Jan 24, 2023 EOL
9 9.52.21 Feb 6, 2024 EOL
10 10.50.2 Feb 4, 2025 EOL
11 11.51.0 Mar 12, 2026 EOL

What does Laravel 12 end of life mean?

When Laravel 12 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Laravel 12 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Laravel 13 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Laravel 12 reach end of life?
Laravel 12 reached end of life on February 24, 2027. That is 291 days remaining.
Is Laravel 12 still supported?
Yes, Laravel 12 is currently supported. The EOL date is February 24, 2027.
What should I upgrade to from Laravel 12?
The recommended upgrade from Laravel 12 is Laravel 13 — the latest actively supported version. Check the Laravel full timeline for all supported versions.
What are the security risks of running Laravel 12 past EOL?
When Laravel 12 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Laravel should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →