Owning software · 5 min

Laravel 11 end of life: no security fixes since 12 March 2026

Laravel 11 has had no security fixes since 12 March 2026, and Laravel 12 follows on 24 February 2027. What it means for your app, and a safe way to Laravel 13.

Published
Reading time
5 min

Short answer: Laravel 11 has had no security fixes since 12 March 2026. Laravel 12 gets them until 24 February 2027. If your app is on either, plan the move to Laravel 13, which is supported until 17 March 2028. It needs PHP 8.3 or newer, so PHP usually moves too.

What "no security fixes" means

Your app still works. Nothing switched off on 12 March.

What changed is what happens the next time a security hole is found in the framework. The Laravel team fixes it in the versions it still supports, and Laravel 11 isn't one of them. The hole stays open in your app until you move.

The dates

From Laravel's support policy, as of 22 November 2026:

Laravel Runs on PHP Security fixes until
10 8.1 to 8.3 4 February 2025 (ended)
11 8.2 to 8.4 12 March 2026 (ended)
12 8.2 to 8.5 24 February 2027
13 8.3 to 8.5 17 March 2028

Laravel releases a new major version every year, and each one gets security fixes for two years. Standing still means falling out of support every year or two.

It's usually two moves, not one

Laravel 13 needs PHP 8.3 or newer. Laravel 11 apps can run on PHP 8.2, and PHP 8.2 loses its own security fixes on 31 December 2026. So the framework and PHP move together, and the server software often moves with them. We wrote up what PHP 8.2's end of life means separately.

Step by step, with a way back

Go one major version at a time: 11, then 12, then 13. At each step:

  1. Update the framework and the packages that depend on it.
  2. Run the tests, then check by hand the parts of the app people use most.
  3. Release, and keep the previous version ready to switch back to.

Before the first step, restore a backup once, so you know it works. If the app has few tests, write some for the parts that make money before you start: they're what tells you an update broke something.

We run this on our own platform first. SportPoint, the platform Daniel co-founded, has run Laravel 13 in production since 28 October 2026, with releases that cause no downtime.

Where we fit

With Security and updates, we take a Laravel, PHP or Node application onto supported versions in one or two weeks, tested, with a way back if anything goes wrong. It starts with a free version check. It isn't a penetration test, and it isn't a guarantee.

Sources: Laravel's support policy and PHP's supported versions, as of 22 November 2026.

Already have software?

A written verdict in 3 to 5 working days, from €1,800: keep, fix or rebuild, and what to do first. Credited if we carry on together within 60 days.