Laravel 10 · Version Status
Laravel 10 End of Life Date
Laravel 10 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Laravel 10 is past end of life. This version no longer receives security patches. 551 days past EOL — migrate to a supported version immediately.
EOL Date
Feb 4, 2025
551 days past EOL
Latest Release
10.50.2
Standard release
Release Date
Feb 14, 2023
Laravel 10 series
Lifecycle detail
Laravel 10 was released on February 14, 2023 and support ended on February 4, 2025 — a supported lifespan of 2 years, in line with the 2 years median for Laravel releases. It was not an LTS release; Laravel reserves longer patch windows for its LTS versions. The last patch it will ever receive is 10.50.2, published February 15, 2026 — 1 year after the published end-of-life date. It has been without security patches for 1 year and 6 months. 2 newer Laravel releases have shipped since.
Attack Surface
20/30 High tier
CISA KEV Exposure
0/20 Not in 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 10 support is available
Commercial vendors offer security patches beyond EOL. 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.21 |
Feb 6, 2024 |
EOL |
| → 10 |
10.50.2 |
Feb 4, 2025 |
EOL |
| 11 |
11.55.0 |
Mar 12, 2026 |
EOL |
What does Laravel 10 end of life mean?
When Laravel 10 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 10 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 10 reach end of life?
Laravel 10 reached end of life on February 4, 2025. This version is no longer receiving security patches.
Is Laravel 10 still supported?
No. Laravel 10 reached end of life on February 4, 2025 and is no longer receiving security patches.
What should I upgrade to from Laravel 10?
The recommended upgrade from Laravel 10 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 10 past EOL?
When Laravel 10 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.