LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23524: Laravel Redis Horizontal Scaling Insecure Deserialization

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

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-23524 is a critical Laravel Reverb issue that can allow remote code execution when Reverb horizontal scaling is enabled and Redis channel data is processed unsafely. Organizations using Laravel Reverb should prioritize checking version, scaling configuration, and Redis exposure. The vendor states the issue is fixed in Reverb 1.7.0.

Executive priority

Treat as urgent for Laravel Reverb environments, especially internet-facing applications or shared Redis infrastructure. Prioritize upgrade and Redis access controls. If Reverb is not used, or scaling is disabled, business exposure is likely lower but should still be validated.

Technical view

Laravel Reverb versions 1.6.3 and below pass Redis channel data into PHP unserialize() without restricting allowed classes. This is CWE-502 insecure deserialization and is rated CVSS 9.8. Exposure is limited to deployments with REVERB_SCALING_ENABLED=true. The advisory highlights greater exploitability where Redis lacks authentication or is network-accessible.

Likely exposure

Most likely exposed systems are Laravel applications using Reverb below 1.7.0 with horizontal scaling enabled. Risk increases if Redis is unauthenticated, reachable from untrusted networks, or not limited to a private network or local loopback.

Exploitation context

The source bundle does not show confirmed active exploitation, and this CVE is not marked KEV. The issue is still high urgency because it is network-reachable, requires no authentication per CVSS, and can lead to remote code execution in affected scaling configurations.

Researcher notes

Key conditions are Reverb <1.7.0, horizontal scaling enabled, and Redis message handling through unsafe unserialize(). The fix is referenced in commit 9ec26f8 and release v1.7.0. Do not assume all Laravel applications are affected; this is specific to Laravel Reverb and scaling logic.

Mitigation direction

  • Upgrade Laravel Reverb to version 1.7.0 or later.
  • Require a strong Redis password.
  • Restrict Redis to a private network or local loopback.
  • Set REVERB_SCALING_ENABLED=false if only one Reverb node is used.
  • Review Laravel and Reverb vendor guidance for deployment-specific instructions.

Validation and detection

  • Inventory applications using Laravel Reverb.
  • Confirm installed Reverb version is 1.7.0 or later.
  • Check whether REVERB_SCALING_ENABLED is set to true.
  • Verify Redis requires authentication.
  • Confirm Redis is not exposed to untrusted networks.
  • Review release notes and advisory for expected remediation status.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-23524 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-23524Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
laravelreverb< 1.7.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.