Laravel released laravel/framework 12.73.0 and 13.43.0 on November 17, 2026. Among validation and queue changes, the release notes list seven fixes that look security-related: two XSS issues, a bypass of Eloquent's mass assignment protection, a bypass in file validation, a depth limit against denial of service in the JSON Schema deserializer, and one more way around signed URL expiration. As of the afternoon of November 17, none of them had a GitHub advisory or a CVE.
Last week, writing about temporary signed URLs that might not expire, I noted that the protection against array-form expires values and the fix for the EncodedParameter regression were on the 12.x branch but in no published release. Both have now shipped (PRs #62411 and #62417).
What the fixes change
The PRs have no description; the behavior shows up in the code and in the tests that come with each one.
- Before #62503,
ComponentAttributeBagskipped escaping for any object passed as an attribute value. AStringable(whatStr::of()returns) containing quotes was printed raw into the HTML. The test usesx" onmouseover=alert(1) data-x="as atitlevalue. Now onlyHtmlableobjects, such asHtmlString, skip escaping, andprepends()values follow the same path. - Before #62499, the
$guardedcheck compared the literal key name. With a model that guardsis_adminand defines asetIsAdminAttribute()mutator,fill(['is-admin' => true])passed the check and reached the mutator, because Eloquent normalizes the name before resolving the attribute. The fix also compares the normalized form. - Before #62504, when a request carried an empty text field and a file under the same name,
$request->all()handed the text to validation, and rules such asimagemight not inspect the file. Now the file replaces the empty value. - #62418 fixes an XSS on the debug page, in the button that copies the request URL. It only appears with
APP_DEBUGon, which in production is already a problem in itself. - #62498 limits
$refdepth inIlluminate\JsonSchema\Deserializerto prevent denial of service through chained schemas.
Who should look first
Every Laravel 12 or 13 application should update, but three profiles are more directly exposed. Models that use $guarded instead of $fillable and fill request data with fill() or create(), especially when the guarded field has a mutator. Blade components that receive user text through Str::of() or another object and pass it into $attributes->merge(). Upload forms validated with $request->validate() where the file type rule is the only barrier before saving.
Laravel 11 and earlier get nothing. Security support for version 11 ended on March 12, 2026, and anyone still on it keeps these flaws open. That is the cost of treating migration as something that can wait while the version is still supported. Laravel 12 receives security fixes until February 24, 2027.
What to do now
Update laravel/framework to 12.73.0 or 13.43.0, run the tests and deploy. There is no external deadline for these flaws, but the fix code has been public since November 17 and shows anyone looking where each one was.
Two things to watch on 13.x. The framework's composer.json now declares a conflict with laravel/horizon below 5.47.0 (#62449), so Composer will require updating Horizon too. It is also worth searching the code for $guarded models fed by $request->all(): switching to $fillable or $request->validated() reduces reliance on that check, with or without the fix.
What is still unknown
There is no advisory, CVE or severity rating for the November 17 fixes. The branches behind the mass assignment and upload PRs carry a SECO- prefix, which suggests internal security tracking, but Laravel has not confirmed this publicly. There is also no information about exploitation in the wild. If advisories come out, they should list the affected version ranges and the exact conditions, which today can only be inferred from the tests.
If your company is weighing something similar, reach me on LinkedIn or WhatsApp.
References
- laravel/framework v12.73.0 (GitHub Releases)
- laravel/framework v13.43.0 (GitHub Releases)
- PR #62503: Fix XSS in component attributes
- PR #62499: Fix Eloquent mass-assignment guard bypass via mutator attribute-name normalization mismatch
- PR #62504: Fix file validation bypass with empty input field collisions
- PR #62411: Prevent array expires parameters from bypassing signed URL expiration
- laravel/framework security advisories
- Laravel 13.x: Release Notes, support policy