Laravel 13.43.0
Remember when a Laravel point release meant three Blade fixes and a changelog you could read between sips of coffee? That era is gone. On November 17, 2026 the framework shipped 13.43.0, more than seventy pull requests deep, and the most striking thing about it is how little of the volume is new surface area. Most of the release is correction: security hardening, validation semantics, and queue edge cases. The 12.x branch received its own bundle the same afternoon as 12.73.0.
The cadence tells its own story. 13.39.0 landed October 27, 13.42.0 on November 10, and 13.43.0 seven days later. Weekly trains, each one carrying the merged output of both branches, with the older line still actively patched. That is the shape of a framework that has stopped arguing about direction and started arguing about correctness.
Security work outnumbers features
Twelve months ago a release like this would have led with a new facade. Instead the headline items are escapes and bypasses.
- XSS in the debug page. The "copy request URL" control could be coaxed into executing script content (#62418). Debug pages are dev-only in theory and reachable in practice, so this one matters more than its scope suggests.
- XSS in component attributes. Bound attributes were not escaped consistently with static ones, which allowed markup injection through component props (#62503).
- Mass assignment guard bypass. A mismatch between how mutator attribute names were normalized and how guarded attributes were compared let certain assignments slip past
$guarded(#62499). If you rely on guards rather than explicit$fillablelists, audit your models. - File validation bypass. Collisions between empty input fields could defeat file validation rules (#62521).
- Deserializer DoS.
Illuminate\JsonSchema\Deserializernow bounds$refchain depth, closing a recursion denial-of-service (#62498). - Signed URL expiration bypasses. Two separate routes were closed: numeric query-fragment parameter smuggling (#62401) and array values in the
expiresparameter (#62411). Both allowed a temporary URL to outlive its window. - Escaping bypass. A general fix prevents escaping from being neutralized by nested encoding (#62027).
None of these are theoretical. Each is the kind of defect that surfaces in a penetration test report six months after the code shipped, and each is worth a line in your upgrade notes even though none requires a code change on your side.
Validation semantics get stricter
The validation component absorbed the largest cluster of fixes, and the pattern is consistency: rules that used to pass when they should have failed now fail.
- not_regex no longer passes when the pattern match itself errors (#62427).
- Wildcard rules stop skipping empty array keys (#62409), and nested
sometimesrules no longer get dropped when the value is__missing__(#62402). - Decimal rule switched to possessive quantifiers (#62421), which trims backtracking on hostile input.
- Fluent database rules compare
where()values literally instead of coercing them (#62425). - exists and unique rules keep every condition on the same column, including in the string variants (#62442, #62459).
- Presence verifier compares integers and booleans as strings (#62447), matching how the database actually stores them.
- Email validation now enforces RFC 5321 address shape rather than accepting anything with an
@in it (#62347).
Alongside the fixes, JsonSchema::rules() arrives as a new way to derive Laravel validation rules directly from a JSON Schema document (#62355), with support for exclusiveMinimum and exclusiveMaximum (#62496) and strict scalar comparison for uniqueItems (#62495). It is the first genuinely new capability in the validation namespace in this cycle.
Queue retries learn policy
Two additions target jobs that fail in interesting ways. The #[RetryFor] attribute lets a job declare a total retry window instead of counting attempts (#62434), and releaseUsingBackoff() on InteractsWithQueue releases a job with a computed delay in one call (#62435). Both are small, both remove boilerplate that every long-running queue codebase eventually grows by hand.
Redis users got two operational fixes with the same flavour: tagged cache reads are now pipelined (#62451), and idempotent Predis commands retry after a dropped connection (#62406). Connection also gained withoutAffectingStickiness() for read and write routing (#62465).
The smaller stuff that breaks deployments
The unglamorous items are the ones that show up in production.
trans_choice()no longer ignores conditions placed after the|separator (#62519).withCasts()applies toRelation::create()again (#62517).touch()on a query with joins no longer produces an ambiguousupdated_atcolumn (#62412).- Union queries with cursor pagination and an aliased order expression paginate correctly (#62433).
Arr::forget()stops removing the wrong element (#62410).schedule:list --jsonreturns each event's own expression and timezone (#62358).- Dropping all tables on PostgreSQL ignores extension-owned tables (#62460).
- The PHP 8.5 deprecation triggered by
from()with a subquery and no alias is silenced (#62430), and Windows path separators resolve inside a running phar (#62413).
What the trajectory says
Three releases in three weeks, most of the diff spent on validation and security rather than features, and a hard conflict declared against laravel/horizon < 5.47.0 (#62449). That last item deserves attention before you upgrade: Composer will refuse the install if your Horizon is older than that, and the fix is a Horizon update, not a framework rollback.
For anyone tracking the 13.x line, the pattern is worth naming. The framework is in its consolidation phase: the feature surface is stable, and the work has moved to making existing behaviour predictable under adversarial input. Historically, that is the phase where Laravel releases age well.
Upgrade notes
- Run
composer update laravel/frameworkor pin"^13.43.0". No migration or config changes are required. - Check
laravel/horizonfirst. Anything below 5.47.0 conflicts. - If you rely on guarded models rather than
$fillable, run your mass assignment tests again (see #62499). - Applications on the 12.x branch get the same fixes in 12.73.0.
Nothing in 13.43.0 will make you rewrite code. Several things in it will stop code that should never have worked, which is the better kind of release.