laravel · Laravel · published 2026-11-13
CVE-2026-128083Laravel: Task Output Injection - Concurrency Process
Routine No exploitation evidence; EPSS 0.7%.
CVE-2026-128083 is not known to be exploited in the wild. EPSS estimates a 0.7% chance of exploitation in the next 30 days, higher than 54% of all CVEs. This Laravel vulnerability: CVSS 2.3 (v4.0), a successful attack gives total control of the component. Fixed upstream in Laravel 13.40.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Laravel 13.40.0.
Patch events
Web frameworkLaravel
Laravel security release: 13.40.0
Upgrade to
13.40.0Why: Vendor security release for server software (most severe: CVE-2026-128083).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.7% (54th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 2.3 (v4.0)CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- laravel framework
>= 13.0.0, < 13.40.0(affected)< 12.71.0(affected)
Description (from the CVE record)#
Laravel is a web application framework. Prior to 12.71.0 and 13.40.0, Laravel's Concurrency::run process driver can treat a forged internal result message in child standard output as framework output. An application route must invoke Concurrency::run, and a task must write attacker-controlled bytes at the start of the child's standard output that form a complete JSON document followed by gzip magic bytes. Under those application-specific conditions, an attacker can forge the internal result message and achieve remote code execution. The affected behavior is not exposed by default and requires application code that routes untrusted input into task output. This issue is fixed in versions 12.71.0 and 13.40.0.
Quoted from the CVE Program record.