Home

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).

PUBLISHED Reserved 2026-01-13 | Published 2026-01-21 | Updated 2026-01-22 | Assigner GitHub_M




CRITICAL: 9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Problem types

CWE-502: Deserialization of Untrusted Data

Product status

< 1.7.0
affected

References

github.com/...reverb/security/advisories/GHSA-m27r-m6rx-mhm4

github.com/...ommit/9ec26f8ffbb701f84920dd0bb9781a1797591f1a

cwe.mitre.org/data/definitions/502.html

github.com/laravel/reverb/releases/tag/v1.7.0

laravel.com/docs/12.x/reverb

cve.org (CVE-2026-23524)

nvd.nist.gov (CVE-2026-23524)

Download JSON