Laravel 12 is already past the first deadline. Its bug fixes ended on August 13, 2026, and it now gets security fixes only. Those end on February 24, 2027. After that date, a newly found security hole in Laravel 12 stays open unless you move to a newer version.
The move is to Laravel 13, which came out on March 17, 2026. Laravel's own upgrade guide estimates about 10 minutes of work. For a real app the larger job is usually PHP, because Laravel 13 needs PHP 8.3 or newer. Here's how to check where you are and upgrade without surprises.
Check your version in a minute.
Run one of these from your project folder:
php artisan --versionprints the Laravel version.composer show laravel/frameworkprints the installed version and its details.php -vprints the PHP version your command line uses. Your web server can run a different PHP, so also check it in your hosting panel.
If the first two show 12.x, you're on Laravel 12. If they show 11.x or older, skip to the table below, because you're already past the end.
The support dates.
Laravel gives each release 18 months of bug fixes and 2 years of security fixes. These are the dates from Laravel's release notes:
| Laravel | PHP versions | Bug fixes until | Security fixes until |
|---|---|---|---|
| 11 | 8.2 to 8.4 | September 3, 2025 | March 12, 2026 (ended) |
| 12 | 8.2 to 8.5 | August 13, 2026 (ended) | February 24, 2027 |
| 13 | 8.3 to 8.5 | Q3 2027 | March 17, 2028 |
Your app keeps running when support ends. What stops is the flow of fixes. Laravel 12 won't get bug fixes at all now, and after February 24, 2027 it won't get security fixes either.
What changes in Laravel 13.
Laravel says it kept breaking changes to a minimum this time, and that most apps can upgrade without changing much code. The one hard requirement is PHP 8.3 or newer. Laravel 12 ran on PHP 8.2, so if your server is still on 8.2, the PHP update comes first. See our guide on checking your PHP version for the dates on each PHP release.
New in 13 are a first-party AI SDK, JSON:API resources and vector search support. You don't need any of them to upgrade.
What can break.
Laravel's upgrade guide ranks each change by how likely it is to affect you. These are the ones worth checking first.
| Impact | Change | What to check |
|---|---|---|
| High | Dependencies | composer.json needs laravel/framework ^13.0, laravel/tinker ^3.0, phpunit/phpunit ^12.0 and pestphp/pest ^4.0, plus laravel/boost ^2.0 if you use it. |
| High | CSRF middleware renamed | VerifyCsrfToken is now PreventRequestForgery and also checks the Sec-Fetch-Site header. The old names still work as deprecated aliases. Update any place you exclude it, especially in tests. |
| Medium | Cache serializable_classes | The new default is false. If you store PHP objects in the cache, list their classes, or they won't load back. |
| Medium | MySQL or MariaDB upsert | An empty uniqueBy now throws an exception. |
| Low | Cache prefixes and session cookie name | Defaults now use hyphens. If you rely on the defaults, cache keys and the session cookie name change. Set CACHE_PREFIX, REDIS_PREFIX and SESSION_COOKIE to keep the old ones. |
| Low | Session serialization | If you copy the new skeleton's config/session.php and switch from php to json, every logged-in user is signed out. |
| Low | Queue events and MySQL deletes | JobAttempted and QueueBusy changed properties. A MySQL DELETE with JOIN now keeps its ORDER BY and LIMIT. |
| Low | Global helper clash | On PHP below 8.5, a polyfill defines array_first() and array_last(). This can clash with laravel/helpers or your own helpers of the same name. |
The guide also lists many very-low-impact items, mostly for apps that write their own cache stores, queue drivers or dispatchers.
A safe upgrade order.
- Back up the code and the database, and work on a branch.
- Get a green test run on Laravel 12 first. Without tests, write a few for checkout, login and any job that moves money or orders.
- Move PHP to 8.3 or 8.4 on staging while still on Laravel 12. Laravel 12 supports both, so this isolates PHP problems from Laravel problems.
- Update
composer.jsonwith the versions from the table, then runcomposer update. - Work through the upgrade guide from high impact to low. Search the code for the names listed, such as
VerifyCsrfTokenandserializable_classes. - Check third-party packages. Each one must allow Laravel 13 in its own
composer.json. An abandoned package is a reason to replace it. - Run the tests, then click through login, forms, queued jobs, scheduled tasks and emails on staging.
- Deploy at a quiet hour, watch the logs and keep the old release ready to roll back to.
The last step to plan for: if the app is a client's, agree on who is on call after the deploy.
If you can't upgrade yet.
You have until February 24, 2027 for security fixes on Laravel 12, but don't spend that time idle. The PHP update and the package check are the slow parts, and they can start now. Agencies with several Laravel clients can have us run the upgrade as white-label Laravel work under their own name.
Want us to handle it?
We handle the tech side. We check your Laravel and PHP versions, upgrade a staging copy, fix whatever breaks, then deploy to production and test with you.
Talk to us about a Laravel upgrade