CVE-2018-15133: Laravel App Key Deserialization RCE
- Vendor
- Laravel
CVE-2018-15133 is an unsafe deserialization vulnerability affecting Laravel Framework through 5.5.40 and the 5.6 branch through 5.6.29. The decrypt method in Illuminate\Encryption\Encrypter can unserialize attacker-controlled data supplied through the X-XSRF-TOKEN request header. An attacker who knows the application's APP_KEY can forge an encrypted serialized payload and use a compatible PHP object gadget chain, including one involving PendingBroadcast, to achieve remote code execution.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary PHP code or command execution on the server hosting the vulnerable Laravel application. Observed exploitation by Androxgh0st has supported malicious payload downloads, sensitive configuration theft, file uploads, and remote access. The vulnerability requires knowledge of the application encryption key; key disclosure or reuse can therefore turn a separate exposure into server-side code execution.
Mitigation
If you can’t patch tonight, do this now.
Prevent unauthorized access to application configuration and encryption keys, disable debug and testing modes on internet-accessible Laravel applications, and restrict unnecessary web access. Use intrusion detection and firewall controls to identify or block malicious requests. These measures reduce exposure but do not replace upgrading the vulnerable framework.
Remediation
Patch, then assume compromise.
Upgrade Laravel Framework to version 5.6.30 or a later fixed release. Protect the application encryption key and replace exposed or reused keys with newly generated, application-specific keys. Investigate potentially compromised deployments for unauthorized code and credential access, and revoke exposed credentials.
Exploits
7 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2018-15133 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jan 16, 2024.
- Is there a public exploit for CVE-2018-15133?
- Yes. Mallory tracks 7 public exploits or proofs of concept for CVE-2018-15133, the earliest disclosed Aug 7, 2018.
- Is there a patch for CVE-2018-15133?
- Upgrade Laravel Framework to version 5.6.30 or a later fixed release. Protect the application encryption key and replace exposed or reused keys with newly generated, application-specific keys.
- What products are affected by CVE-2018-15133?
- Laravel.
- How severe is CVE-2018-15133?
- CVE-2018-15133 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 76.6% (100th percentile) as of Oct 16, 2026.
Recent activity
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.