# CVE-2026-48019: CRLF injection in Laravel's default email rule enables SMTP smuggling and spoofed-mail relay

> Unauthenticated attackers can inject CRLF sequences to smuggle SMTP commands and spoof emails in Laravel applications sending mail to user-supplied addresses.

- **Severity:** High 8.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** CLSA-2026-1782954027, CLSA-2026-1782954039, CLSA-2026-1783040462, CLSA-2026-1783299702, CLSA-2026-1783299711, CLSA-2026-1783558965, CLSA-2026-1784077480, CLSA-2026-1784077484, CLSA-2026-1784250514, CLSA-2026-1784682984, CLSA-2026-1784682989, CLSA-2026-1785380807, CLSA-2026-1786014841, CLSA-2026-1786443515, CLSA-2026-1787229037, DEBIAN-CVE-2026-48019, GHSA-5vg9-5847-vvmq

## What is CVE-2026-48019?

CVE-2026-48019 is a high-severity vulnerability in laravel framework, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

## Which versions are affected by CVE-2026-48019?

4 open source packages ship an affected version, including laravel/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `laravel/framework` | Packagist | All versions | 12.60.0 |
| `laravel/framework` | Packagist | All versions | 12.60.0 |
| `laravel/framework` | Packagist | From 13.0.0 | 13.10.0 |
| `laravel/framework` | Packagist | From 13.0.0 | 13.10.0 |

## How do I fix CVE-2026-48019?

Upgrade laravel/framework to a fixed version for your release line: 12.60.0 or 13.10.0.

## Is CVE-2026-48019 being exploited?

There is no known exploitation of CVE-2026-48019 in the wild and no public exploit code.

Public exploit code:

- Fork of laravel/framework 10.50.2 with CVE-2026-48019 (CRLF injection in default email rule) backported into ValidatesAttributes::validateEmail. Tagged 10.51.0. (github_poc): https://github.com/derrickschoen/laravel-framework

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48019 and fix it if it is affected.

What it is: CVE-2026-48019 is a high-severity vulnerability in laravel framework, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48019 in the wild and no public exploit code.

Affected packages and fixed versions:
- laravel/framework (Packagist): affected all versions; fixed in 12.60.0
- laravel/framework (Packagist): affected all versions; fixed in 12.60.0
- laravel/framework (Packagist): affected from 13.0.0; fixed in 13.10.0
- laravel/framework (Packagist): affected from 13.0.0; fixed in 13.10.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48019/ (Markdown: https://insights.sbomify.com/CVE-2026-48019/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48019
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48019
- OSV: https://osv.dev/vulnerability/CVE-2026-48019

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48019/
Summaries are generated and may contain mistakes; the official description above is the record.