LARAVEL COVERAGE
Laravel 11 and 10 are out of support. Your patching does not have to be.
Laravel extended support from OSSeva covers Laravel versions past the security-fix dates in Laravel's support policy. Laravel 11 security fixes ended on 12 March 2026 and Laravel 10 on 4 February 2025, and Laravel 12 is already security-only. Send your work email and an engineer replies within 1 business day with coverage for your Laravel version.
| Who it is for | Teams running Laravel 10 or 11 whose upgrade to 13 is blocked by a PHP upgrade, a package that has not moved or a release freeze |
|---|---|
| What you get | Signed patched laravel/framework releases on your line, with your composer.json constraints, public API and Eloquent behaviour unchanged. Assure adds an exposure audit, an upgrade path assessment and 24/7 reactive support. |
| How it is priced | Per application. Ask for a quote. |
| What happens next | You send your work email, we confirm your Laravel and PHP versions and which first-party packages you use, and you get a coverage plan. |
Reply within 1 business day · No commitment · or book a 15-minute call
Last reviewed
Trusted globally by enterprises





Laravel support dates, read on 19 November 2026
Laravel gives every release 18 months of bug fixes and 2 years of security fixes. Only the framework follows that policy: for first-party packages, the policy page says only the latest major release gets bug fixes.
| Version | Released | Bug fixes until | Security fixes until | PHP |
|---|---|---|---|---|
| 10 | 14 Feb 2023 | 6 Aug 2024 | 4 Feb 2025 | 8.1 to 8.3 |
| 11 | 12 Mar 2024 | 3 Sep 2025 | 12 Mar 2026 | 8.2 to 8.4 |
| 12 | 24 Feb 2025 | 13 Aug 2026 | 24 Feb 2027 | 8.2 to 8.5 |
| 13 | 17 Mar 2026 | Q3 2027 | 17 Mar 2028 | 8.3 to 8.5 |
Source: laravel.com/docs/releases (support policy table). endoflife.date lists the same dates. Laravel has no long-term-support release in this range: endoflife.date marks 6 as the last one.
Laravel end-of-life dates for every version →laravel.com: support policy →
Laravel and the PHP under it
Moving a Laravel application off an ended line usually means moving PHP as well. Laravel 12 needs PHP 8.2 or newer and Laravel 13 needs PHP 8.3 or newer, per the support policy table.
- Laravel 10 on PHP 8.1: PHP 8.1 ended on 31 December 2025, so both layers are unsupported. See [PHP 8.1 end of life](/eol/php-8-1).
- Laravel 11 on PHP 8.2: PHP 8.2 ends on 31 December 2026, six weeks from this page's read date. See [PHP 8.2 end of life](/eol/php-8-2).
- Laravel 13 requires PHP 8.3, so a Laravel 11 site on PHP 8.2 cannot reach the newest line without a PHP upgrade first.
PHP extended support →PHP end-of-life dates →PHP extended support for 7.4 to 8.3 →
Why now
Laravel 11 lost security fixes on 12 March 2026
The Laravel support policy lists security fixes for Laravel 11 until 12 March 2026. Laravel gives every release 18 months of bug fixes and 2 years of security fixes, and 11 is now past both.
Laravel 12 is already security-only
Bug fixes for Laravel 12 ended on 13 August 2026 and security fixes run to 24 February 2027.
A PHP end of life sits under the Laravel one
Laravel 10 runs on PHP 8.1 to 8.3 and Laravel 11 on PHP 8.2 to 8.4. PHP 8.1 ended on 31 December 2025 and PHP 8.2 ends on 31 December 2026, so an application on either Laravel line is often on a PHP that is ending or ended too.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 10(Security fixes ended 4 Feb 2025) | EOL | See advisories |
| 11(Security fixes ended 12 Mar 2026) | EOL | See advisories |
| 12(Security fixes until 24 Feb 2027. Assessed case by case.) | Current | See advisories |
| 13(Security fixes until 17 Mar 2028. Assessed case by case.) | Current | See advisories |
Running a Laravel version or build not listed here?
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
Security patches for Laravel 11 and 10 after end of life.
- Backported security fixes for Laravel 11 and 10
- Critical CVEs fixed within 48 hours, High within 7 days
- Signed artifacts (GPG + Sigstore)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus compliance documentation and upgrade planning.
- Everything in Patch
- SOC 2 / HIPAA attestation package
- Laravel upgrade path assessment
- 24/7 reactive support
OSSeva Operate
Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.
- Everything in Assure
- 24/7 application and runtime monitoring
- 15-minute P1 incident response SLA
- Named senior engineer on your account
All tiers priced per cluster/application — not per core.
Which Laravel versions does OSSeva patch?
Laravel 11 and 10 after end of life. Other versions are assessed case by case through a version coverage check.
How fast are Laravel vulnerabilities patched?
Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.
Do I need PHP patched as well as Laravel?
Often yes. Laravel 10 needs PHP 8.1 or newer and Laravel 11 needs PHP 8.2 or newer, and PHP 8.1 has ended while 8.2 ends on 31 December 2026. The runtime and the framework are patched separately: see PHP extended support for the runtime.
How is OSSeva Laravel support priced?
It is priced per application. Request a quote and a senior engineer replies within 1 business day.
Get a quote
Ready to get Laravel patched and supported?
Tell us your Laravel versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.
Prefer to talk or read more first?