CVE-2026-23524
RCE via unsafe unserialize in Laravel Reverb <=1.6.3 when scaling with Redis.
Is CVE-2026-23524 being exploited?
Not confirmed. CVE-2026-23524 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.91% probability of exploitation in the next 30 days.
How severe is CVE-2026-23524?
CVE-2026-23524 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-23524?
Yes. A fix has been recorded for CVE-2026-23524. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-23524 affect?
CVE-2026-23524 affects Laravel Reverb <= 1.6.3, Redis deployment with REVERB_SCALING_ENABLED=true. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-23524?
Upgrade to 1.7.0; enforce Redis auth and private network.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via deserialization of Redis data; attacker could run code on host.
Immediate action required
- affected< 1.7.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.