CVE-2026-23524: laravel reverb · Deserialization of Untrusted Data
Affects laravel reverbSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.7.0 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.7.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade reverb and laravel/reverb to 1.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| laravelreverb | Affected
| Fixed in
|
GitHublaravel/reverbpkg:github/laravel/reverbOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade Laravel Reverb to version 1.7.0 or later immediately to apply the official patch that fixes the deserialization vulnerability. 2. Enforce strong authentication on Redis servers by configuring robust passwords and enabling Redis ACLs to restrict access. 3. Restrict Redis access to private networks or localhost interfaces to prevent unauthorized external connections. 4. If horizontal scaling is not required, set REVERB_SCALING_ENABLED=false to disable the vulnerable deserialization logic. 5. Implement network segmentation and firewall rules to isolate Redis servers from untrusted networks. 6. Monitor Redis channels and application logs for suspicious serialized payloads or unusual activity indicative of exploitation attempts. 7. Conduct regular security audits and penetration tests focusing on deserialization vulnerabilities and Redis configurations. 8. Educate development and operations teams about secure serialization practices and the risks of deserializing untrusted data. 9. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block malicious serialized payloads targeting PHP unserialize functions. 10. Maintain an incident response plan to quickly address potential exploitation events involving Laravel Reverb.
Description
CVE-2026-23524 is a critical deserialization vulnerability in Laravel Reverb versions below 1.7.0 that allows unauthenticated remote code execution. The flaw arises because data from Redis channels is passed directly into PHP's unserialize() function without class restrictions, enabling attackers to instantiate malicious objects. Exploitation is facilitated by the common practice of deploying Redis without authentication and occurs only when horizontal scaling is enabled (REVERB_SCALING_ENABLED=true). The vulnerability impacts confidentiality, integrity, and availability with a CVSS score of 9.8. Mitigation includes upgrading to Laravel Reverb 1.7.0 or later, enforcing strong Redis authentication, restricting Redis access to private networks, or disabling horizontal scaling if feasible.
References
- github.com/laravel/reverb/security/advisories/GHSA-m27r-m6rx-mhm4 (opens in a new tab)
- github.com/laravel/reverb/commit/9ec26f8ffbb701f84920dd0bb9781a1797591f1a (opens in a new tab)
- cwe.mitre.org/data/definitions/502.html (opens in a new tab)
- github.com/laravel/reverb/releases/tag/v1.7.0 (opens in a new tab)
- laravel.com/docs/12.x/reverb (opens in a new tab)