VulnSocial

CVE-2026-23524Patch(laravel / reverb)

LOWCVSS 9.8 · CRITICAL

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch laravel reverb systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

Laravel Reverb provides a real-time WebSocket communication backend for Laravel applications. In versions 1.6.3 and below, Reverb passes data from the Redis channel directly into PHP’s unserialize() function without restricting which classes can be instantiated, which leaves users vulnerable to Remote Code Execution. The exploitability of this vulnerability is increased because Redis servers are commonly deployed without authentication, but only affects Laravel Reverb when horizontal scaling is enabled (REVERB_SCALING_ENABLED=true). This issue has been fixed in version 1.7.0. As a workaround, require a strong password for Redis access and ensure the service is only accessible via a private network or local loopback, and/or set REVERB_SCALING_ENABLED=false to bypass the vulnerable logic entirely (if the environment uses only one Reverb node).

laravel CVEsBack to dashboard
0.5/ 10 priority

Sources & remediation

Patch / fix
Vendor / third-party advisories
Other references
Weakness type (CWE)
CWE-502

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • reverb

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 2 signals
  • Disclosure: 1 classified signal
  • Peaked 1d ago at 1 mentions (2026-01-30); latest day: 1
  • 2 total mentions across 2 days

Affected systems

Vendors
laravel
Products
reverb

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-01-30: 1Mentions · 2026-03-06: 1Patch / Workaround · 2026-01-30: 1Technical Details · 2026-01-30: 1Technical Details · 2026-03-06: 101-3003-06
Signal classification2 categories
Patch
150.0%
Disclosure
150.0%
Referenced assets1 URL
Classification over time
DateTotalLabels
2026-01-301
Patch1
2026-03-061
Disclosure1
Full discourse2 posts
  • Mike Webtech Digital@mikewebtech
    Patch

    🚨CRITICAL: If you are using Laravel Reverb with horizontal scaling, you are likely sitting on a 9.8 Severity RCE vulnerability (CVE-2026-23524). Attackers can execute code remotely through insecure Redis deserialization. Here is how to fix it before your app is compromised: 🧵 https://t.co/ngElYsSuqJ

    Post summary

    CVE-2026-23524 is a high‑severity RCE via insecure Redis deserialization in Laravel Reverb; the tweet directs users to apply a patch before exploitation can occur.

    10010109
    586 followersView on X
  • DailyCVE@dailycve
    Disclosure

    🔴 Laravel Reverb, Insecure Deserialization, #CVE-2026-23524 (Critical) https://dailycve.com/laravel-reverb-insecure-deserialization-cve-2026-23524-critical/

    Post summary

    A new critical vulnerability, CVE-2026-23524, has been announced in Laravel Reverb’s insecure deserialization functionality.

    0000034
    164 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Applaravelreverb---

Explore more

Back to dashboardlaravel CVEsreverb vulnerabilities