No. Laravel's support policy lists security fixes for Laravel 11 until 12 March 2026, so it is out of support. Laravel 12 is now in its security-only window until 24 February 2027, and Laravel 13 is the current release. If you are on 11, plan the upgrade now.
The support table
Laravel's release notes publish a table of PHP versions and support dates. The 12.x documentation shows:
| Laravel | PHP | Released | Bug fixes until | Security fixes until |
|---|---|---|---|---|
| 10 | 8.1 to 8.3 | 14 February 2023 | 6 August 2024 | 4 February 2025 |
| 11 | 8.2 to 8.4 | 12 March 2024 | 3 September 2025 | 12 March 2026 |
| 12 | 8.2 to 8.5 | 24 February 2025 | 13 August 2026 | 24 February 2027 |
| 13 | 8.3 to 8.5 | Q1 2026 | Q3 2027 | Q1 2028 |
The page also notes that Laravel and its first-party packages follow Semantic Versioning, that major releases arrive about once a year in the first quarter, and that only the latest major release receives bug fixes. It shows a banner on the 12.x page recommending an upgrade to 13.x.
Two details in the table affect planning. The Laravel 13 row shows quarter-level dates for its later windows, so refresh the figure when exact dates appear. And Laravel 13 needs PHP 8.3 or higher, which links the framework move to the runtime move.
Why a framework date is its own inventory row
A framework end date is separate from the language runtime date, even though they interact. Laravel 11 at March 2026 and PHP 8.2 at 31 December 2026 are two different clocks. If you track only PHP, you will miss an unsupported framework that still runs on a supported PHP. For the language side see PHP 8.1 and 8.2 dates.
Packages around the framework matter too: first-party packages follow their own versions, and third-party packages follow the maintainers' choices. A lock file records exact versions. Composer's audit command can flag known advisories and abandoned packages, which composer audit in CI explains.
Upgrade steps for a Laravel 11 app
- Check PHP. Laravel 12 supports 8.2 to 8.5, and Laravel 13 supports 8.3 to 8.5, so decide your PHP target first.
- Upgrade to 12 first if your PHP is 8.2, then to 13 after the runtime moves.
- Read the official upgrade guide for each major. Change one major at a time.
- Update third-party packages to versions that declare support for the target.
- Run tests, then a staging soak, then a gradual rollout.
What to record
- Framework and exact version, from the lock file.
- Support phase: bug fixes, security only, or unsupported.
- The dates from the official table, with the check date.
- Owner, target version and target date.
Use five lifecycle statuses so every row speaks the same language.
Try it yourself
Click through it at your own pace, or open it full screen. Notice that the framework is one entry among many, which is why it needs its own lifecycle field.
Where Safeguard fits
Safeguard's SBOM and dependency scanning lists your Composer packages from the lock file, and its autonomous remediation can open fix PRs for vulnerable dependencies, off by default, with every category on Manual until you change it. Try the free scan at gold.safeguard.sh/scan.
Quick check
Is Laravel 12 still getting security fixes?
Yes, until 24 February 2027 per the support table.
Can I stay on 11 if I patch PHP?
Patching PHP does not give the framework fixes. Laravel 11 security fixes ended on 12 March 2026.
Sources
Last reviewed: 19 October 2026.
