Laravel 12 · Version Status
Laravel 12 End of Life Date
Laravel 12 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚡
Laravel 12 reaches end of life on February 24, 2027. Plan your migration now — 109 days remaining.
📅 Get reminded before Laravel 12 reaches EOL on February 24, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Feb 24, 2027
109 days remaining
Latest Release
12.71.0
Standard release
Release Date
Feb 24, 2025
Laravel 12 series
Where these dates come from
End of lifeFeb 24, 2027Vendor's own page, checked by a person · laravel.com · checked Nov 1, 2026high · 2 sources agree End of active supportAug 13, 2026Vendor's own page, checked by a person · laravel.com · checked Nov 1, 2026high · 2 sources agree ReleaseFeb 24, 2025Vendor's own page, checked by a person · laravel.com · checked Nov 1, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Laravel 12 was released on February 24, 2025 and support is scheduled to end on February 24, 2027 — a planned supported lifespan of 2 years, in line with the 2 years median for Laravel releases. It is not an LTS release; Laravel reserves longer patch windows for its LTS releases. Its most recent patch is 12.71.0, published November 3, 2026.
Attack Surface
20/30 High tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Laravel 12 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 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.23 |
Feb 6, 2024 |
EOL |
| 10 |
10.50.4 |
Feb 4, 2025 |
EOL |
| 11 |
11.57.1 |
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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Laravel 12 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 reaches end of life on February 24, 2027. That is 109 days remaining.
Is Laravel 12 still supported?
Laravel 12 is still supported but approaching end of life on February 24, 2027. Begin planning your migration now.
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 vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Laravel should migrate immediately or implement compensating controls.