Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-48019 – CRLF Injection / Outbound Email Manipulation – Laravel Framework (< 12.60.0, 13.0.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-48019 is a CRLF (Carriage Return Line Feed) injection vulnerability in the Laravel Framework’s email validation logic, rated High severity (CVSS 8.9). When an application sends mail to a user-supplied email address, the flaw — combined with how Symfony Mailer and Symfony Mime handle certain character sequences — can let an unauthenticated attacker manipulate outbound email content. No authentication or user interaction is required to trigger it.

Technical details

  • Root cause: Laravel’s validateEmail() logic and the Address handling used by the default email validation rule do not properly neutralize CRLF sequences embedded in user-supplied email address input.
  • Trigger condition: an application accepts a user-supplied email address (e.g., during registration, password reset, or contact forms) and passes it through to outbound mail sent via Symfony Mailer/Symfony Mime, which mishandles the injected sequences.
  • Attack vector: network-based, no privileges or user interaction required, though attack complexity is rated high.
  • Impact: attackers can inject malicious content into outbound emails, potentially redirecting messages, altering mail headers/body, or abusing the application’s mail infrastructure — reflected in the CVSS vector’s Scope: Changed with high confidentiality and integrity impact and low availability impact.

Affected software

  • Laravel Framework versions prior to 12.60.0 (12.x branch)
  • Laravel Framework 13.0.0 through 13.9.x (before 13.10.0)

Severity

  • CVSS v3.1 Base Score: 8.9 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L

Mitigation and recommended actions

  • Immediate: Upgrade laravel/framework to version 12.60.0 or 13.10.0 (or later), whichever branch applies, via composer update laravel/framework.
  • If patching is not immediately possible: add server-side input validation/middleware to reject any user-supplied email or related input containing CR (r) or LF (n) characters before it reaches email-sending logic, as an interim network-layer mitigation.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Set-Cookie response header: laravel_session=
  • Raw response body: a "laravel_version":"<version>" field
  • Rendered page (JavaScript object presence): Laravel

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge