Laravel EOL: end-of-life dates for every Laravel version
Laravel 11 reached end of life on 12 March 2026, when its security fixes ended, and Laravel 10 ended on 4 February 2025. Laravel 12 receives security fixes until 24 February 2027 and Laravel 13 until 17 March 2028. OSSeva patches Laravel 11 and 10 after end of life. Dates checked against laravel.com and endoflife.date on 19 November 2026.
- Latest release
- 13.43.0
- Supported lines
- 2
- End-of-life lines
- 8
- Next end of life
- 12 · 24 Feb 2027
Laravel 11 has ended; 12 is next
Upgrade to Laravel 13, or keep Laravel 10 and 11 patched
Most applications should move to Laravel 13. When a PHP upgrade, a package that has not moved or a release freeze holds a site on an older line, OSSeva patches Laravel 11 and 10 after end of life. Other versions are assessed case by case through a version coverage check. Critical fixes ship within 48 hours and High within 7 days.
Who patches Laravel after end of life
OSSeva provides Laravel extended support: patched, signed builds for Laravel 11 and 10 after upstream support ends, plus 24/7 operations on the Operate tier.
Laravel release timeline
All Laravel versions, release dates and end-of-life dates
| Version | Released | Active Support | Security Support | Latest | OSSeva |
|---|---|---|---|---|---|
| 13 | 8 months ago(17 Mar 2026) | Ends in 10 months(30 Sept 2027) | Ends in 1 year and 4 months(17 Mar 2028) | 13.43.0 | – |
| 12 | 1 year and 9 months ago(24 Feb 2025) | Ended 3 months ago(13 Aug 2026) | Ends in 3 months(24 Feb 2027) | 12.73.0 | – |
| 11 | 2 years and 8 months ago(12 Mar 2024) | Ended 1 year and 3 months ago(3 Sept 2025) | Ended 8 months ago(12 Mar 2026) | 11.57.1 | Patched |
| 10 | 3 years and 9 months ago(14 Feb 2023) | Ended 2 years and 4 months ago(6 Aug 2024) | Ended 1 year and 10 months ago(4 Feb 2025) | 10.50.4 | Patched |
| 9 | 4 years and 9 months ago(8 Feb 2022) | Ended 3 years and 3 months ago(8 Aug 2023) | Ended 2 years and 10 months ago(6 Feb 2024) | 9.52.23 | – |
| 8 | 6 years and 2 months ago(8 Sept 2020) | Ended 4 years and 4 months ago(26 Jul 2022) | Ended 3 years and 10 months ago(24 Jan 2023) | 8.83.29 | – |
| 7 | 6 years and 9 months ago(3 Mar 2020) | Ended 6 years and 2 months ago(6 Oct 2020) | Ended 5 years and 9 months ago(3 Mar 2021) | 7.30.7 | – |
| 6 (LTS) | 7 years and 3 months ago(3 Sept 2019) | Ended 4 years and 10 months ago(25 Jan 2022) | Ended 4 years and 3 months ago(6 Sept 2022) | 6.20.45 | – |
| 5.8 | 7 years and 9 months ago(26 Feb 2019) | Ended 7 years and 3 months ago(26 Aug 2019) | Ended 6 years and 9 months ago(26 Feb 2020) | 5.8.38 | – |
| 5.5 (LTS) | 9 years and 3 months ago(30 Aug 2017) | Ended 7 years and 3 months ago(30 Aug 2019) | Ended 6 years and 3 months ago(30 Aug 2020) | 5.5.50 | – |
Lifecycle data from endoflife.date (MIT licence), refreshed 21 Nov 2026. Upstream policy: laravel.com. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.
Laravel 10, 11, 12 and 13 support dates
Laravel supports every release for 18 months of bug fixes and 2 years of security fixes, so a version is security-only for its last six months. Laravel 12 passed that point on 13 August 2026. The policy has no long-term-support release: endoflife.date marks Laravel 6 as the last one.
Laravel support dates. Sources: laravel.com/docs/releases and endoflife.date, read on 19 November 2026.
| Version | Released | Bug fixes until | Security fixes until | PHP | Latest release |
|---|---|---|---|---|---|
| 10 | 14 Feb 2023 | 6 Aug 2024 | 4 Feb 2025 (ended) | 8.1 to 8.3 | 10.50.4 |
| 11 | 12 Mar 2024 | 3 Sep 2025 | 12 Mar 2026 (ended) | 8.2 to 8.4 | 11.57.1 |
| 12 | 24 Feb 2025 | 13 Aug 2026 | 24 Feb 2027 | 8.2 to 8.5 | 12.73.0, 17 Nov 2026 |
| 13 | 17 Mar 2026 | Q3 2027 | 17 Mar 2028 | 8.3 to 8.5 | 13.43.0, 17 Nov 2026 |
Packagist lists tags v11.57.1 and v10.50.4 dated 27 October 2026, after the policy dates. The support policy does not list either series as receiving security fixes, and we have not reviewed what those tags contain, so treat them as unsupported releases and read the release notes before relying on them.
Upgrading Laravel 10 or 11: what blocks it
The Laravel upgrade guides are written one major at a time, so Laravel 11 to 13 is two passes and Laravel 10 to 13 is three. The 12 to 13 guide estimates 10 minutes and rates only three changes as high impact, but the first pass is usually the hard one, and the first blocker is PHP, not Laravel.
Laravel 12 needs PHP 8.2 or newer and Laravel 13 needs PHP 8.3 or newer. PHP 8.1 ended on 31 December 2025 and PHP 8.2 ends on 31 December 2026. A Laravel 10 site on PHP 8.1 therefore has both layers unsupported today, and a Laravel 11 site on PHP 8.2 can reach Laravel 12 but not 13 without a PHP upgrade, and would then sit on a PHP line that ends in six weeks.
The 12 to 13 changes below are from the Laravel 13 upgrade guide. Two of them are defaults that harden against PHP deserialization attacks, which is why they change behaviour for applications that store objects in cache or sessions.
Changes in the Laravel 12 to 13 upgrade that need attention. Source: laravel.com/docs/13.x/upgrade, read on 19 November 2026.
| Impact | Change | What it breaks |
|---|---|---|
| High | Dependencies: phpunit/phpunit ^12, pestphp/pest ^4, laravel/tinker ^3 | Test suites on PHPUnit 11 or Pest 3 fail to resolve until the constraints move |
| High | VerifyCsrfToken renamed PreventRequestForgery, now checks the Sec-Fetch-Site header | Old class names are deprecated aliases, but tests and routes that exclude the middleware by class need editing |
| Medium | Cache serializable_classes defaults to false | Applications that cache PHP objects must list the classes that may be unserialized, or move to arrays |
| Medium | upsert on MySQL or MariaDB throws on an empty uniqueBy | Calls that passed an empty array stop working |
| Low | Session serialization set to json in the skeleton | Copying the new config while on php serialization signs every user out |
This is not the full list: the guide also covers cache prefixes, queue event renames, domain route precedence and a symfony/polyfill-php85 dependency whose array_first and array_last helpers can collide with older helper packages. Read the guide before you start.
Who patches Laravel after end of life?
Laravel's support policy ends security fixes for each series on a set date; later tags carry no support promise. We looked for other providers: HeroDevs' own support page, read on 19 November 2026, does not list Laravel or Symfony among its products and says coverage expands based on customer demand. OSSeva patches Laravel 11 and 10 after end of life.
Facts from each provider's own page, read on 19 November 2026.
| Provider | Laravel versions the page lists | Fix timing the page states |
|---|---|---|
| HeroDevs | None: Laravel is not on its support page | Not applicable |
| OSSeva | 11 and 10. Other versions case by case | Critical within 48 hours, High within 7 days |
How we compared: HeroDevs' row uses only its own support page. We did not read other providers' pages and have not listed them, so this table does not show that nobody else sells Laravel fixes.
Running an end-of-life Laravel version?
OSSeva keeps end-of-life Laravel patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.
Laravel extended supportIs Laravel 11 end of life?
Yes. Laravel 11 security fixes ended on 12 March 2026, per the Laravel support policy, and bug fixes ended on 3 September 2025. OSSeva patches Laravel 11 after end of life.
When does Laravel 12 reach end of life?
Security fixes for Laravel 12 end on 24 February 2027. Its bug fixes already ended on 13 August 2026, so it now receives security fixes only. The latest 12.x release is 12.73.0 from 17 November 2026.
When does Laravel 13 reach end of life?
Security fixes for Laravel 13 run to 17 March 2028, with bug fixes until Q3 2027. Laravel 13 requires PHP 8.3 or newer.
Is Laravel 10 still supported?
No. Laravel 10 security fixes ended on 4 February 2025. It ran on PHP 8.1 to 8.3, and PHP 8.1 has also ended. See PHP 8.1 end of life.
Which PHP version does Laravel need?
Laravel 10 supports PHP 8.1 to 8.3, 11 supports 8.2 to 8.4, 12 supports 8.2 to 8.5 and 13 supports 8.3 to 8.5. PHP 8.2 ends on 31 December 2026: see PHP 8.2 end of life.
Who provides Laravel support after end of life?
OSSeva patches Laravel 11 and 10 after end of life and assesses other versions case by case through a version coverage check. HeroDevs' support page does not list Laravel, read on 19 November 2026.
What is the latest Laravel version?
13.43.0, released 17 Nov 2026, on the 13 line. Other supported lines: 12.
When is the next Laravel end of life?
Laravel 12 reaches the end of security support on 24 Feb 2027. After that date the project stops shipping security fixes for 12, and CVEs disclosed later stay unpatched upstream.
Which Laravel versions are still supported?
13 (until 17 Mar 2028) and 12 (until 24 Feb 2027). Every other line has reached end of life, per the dates in the table above.
Can I get security patches for an end-of-life Laravel version?
Yes. OSSeva ships signed builds with backported CVE fixes for Laravel 11 and 10 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.
Get a quote
Still running an end-of-life Laravel?
Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.
Prefer to talk or read more first?