laravel/framework security advisory

CVE-2026-48019: Laravel CRLF injection in default email rule

CVE-2026-48019 is a high-severity header injection vulnerability in the PHP package laravel/framework (CVSS 8.9), published 4 September 2026. It is fixed in 12.60.0 and 13.10.0, one per release line; earlier versions on each line are affected. It can be exploited without an account.

high 8.9 published 2026-09-04 · updated 2026-09-10

Affected versions: >= 9.0.0, < 12.60.0
>= 13.0.0, < 13.10.0
Fixed in: 12.60.0, 13.10.0
Newest release: 13.40.0
Severity: High · CVSS 8.9
Type: Header injection
CWE-93
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your laravel/framework version affected?

Run composer show laravel/framework in your project, then enter the version. We check it against this and every other known laravel/framework advisory.

Who can exploit CVE-2026-48019

Access: No account. Anyone who can send a request to an app that uses the affected code.
Conditions: It only works under specific conditions the attacker does not fully control (CVSS rates the attack as high complexity).

CVSS vector (scored by GitHub): CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L

Your app is only exposed if it uses the affected part of laravel/framework. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-48019 in laravel/framework

Find the installed version: composer show laravel/framework. If you never required it yourself, composer why laravel/framework shows which package pulls it in.
Update it: composer update laravel/framework --with-all-dependencies. You need the fixed version for your release line (12.60.0 and 13.10.0).
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "laravel/framework": "^13.10.0" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-48019.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for header injection issues while the upgrade waits. None of it replaces the fix.

Strip CR and LF characters from any user input that ends up in mail or HTTP headers, including parameter names.
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-48019 advisory

Laravel is a web application framework. Prior to versions 12.60.0 and 13.10.0, a CRLF injection vulnerability in Laravel's email validation, in combination with how Symfony Mailer and Symfony Mime handle certain character sequences, may allow an unauthenticated attacker to interfere with outbound email processing in applications that send mail to user-supplied addresses. This issue has been patched in versions 12.60.0 and 13.10.0.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-48019. Advisory title: “Laravel CRLF injection in default email rule”.

References

GitHub security advisory GHSA-5vg9-5847-vvmq github.com
Fix commit 96e9a66 github.com
Fix commit f336ba7 github.com
Pull request #60151 github.com
Release v12.60.0 github.com
Release v13.10.0 github.com

Other laravel/framework advisories

critical CVE-2026-114509: Laravel TokenGuard authentication bypass through non-string API credentials 2026-10-23
medium CVE-2026-114508: Laravel relationship inclusion can trigger unauthorized data destruction 2026-10-23
low CVE-2026-102279: Laravel: XSS in Debug Page Information 2026-09-29
medium Laravel Framework: Temporary Signed URL Path Confusion 2026-06-17
high Laravel Framework: CRLF injection in default email rule 2026-06-17
medium CVE-2025-27515: Laravel has a File Validation Bypass 2025-03-05

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.