CVE-2026-23524

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 45% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
55.3%
KEV
Not listed

Published

January 21, 2026

Last Modified

March 6, 2026

Advisory Details (5)

Auto-updated May 30, 2026
Patch available. Sources: github_commit, github_release, github.
generic

Laravel Reverb | Laravel 12.x - The clean stack for Artisans and agents

https://laravel.com/docs/12.x/reverb#scaling
github Patch Available

Redis Horizontal Scaling Insecure Deserialization · Advisory · laravel/reverb · GitHub

https://github.com/laravel/reverb/security/advisories/GHSA-m27r-m6rx-mhm4
github_release Patch Available

v1.7.0

Patch available: laravel/reverb v1.7.0

https://github.com/laravel/reverb/releases/tag/v1.7.0
github_commit Patch Available

commit 9ec26f8ffbb7 (laravel/reverb)

Patch available: laravel/reverb v1.7.0 (contains commit 9ec26f8ffbb7)

https://github.com/laravel/reverb/commit/9ec26f8ffbb701f84920dd0bb9781a1797591f1a
generic

CWE - CWE-502: Deserialization of Untrusted Data (4.20)

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

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
laravel/reverbv1.0.0 ... v1.6.3 (34 versions)1.7.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 101 total refreshes for this CVE.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:07 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-21 15:24 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 02:29 UTCEPSS rescore
  11. 2026-07-19 02:28 UTCEPSS rescore
  12. 2026-07-18 10:04 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-16 17:03 UTCEPSS rescore
  15. 2026-07-16 17:03 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-13 22:30 UTCEPSS rescore
  21. 2026-07-13 21:08 UTCOSV refresh
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-12 05:46 UTCEPSS rescore
Show 75 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-08 15:15 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-01 15:06 UTCEPSS rescore
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-25 18:46 UTCOSV refresh
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
  26. 2026-06-24 14:05 UTCEPSS rescore
  27. 2026-06-24 14:05 UTCEPSS rescore
  28. 2026-06-23 21:33 UTCEPSS rescore
  29. 2026-06-23 21:32 UTCEPSS rescore
  30. 2026-06-22 14:25 UTCEPSS rescore
  31. 2026-06-22 14:25 UTCEPSS rescore
  32. 2026-06-21 14:56 UTCEPSS rescore
  33. 2026-06-21 14:56 UTCEPSS rescore
  34. 2026-06-21 01:59 UTCEPSS rescore
  35. 2026-06-21 01:59 UTCEPSS rescore
  36. 2026-06-19 19:25 UTCEPSS rescore
  37. 2026-06-19 19:25 UTCEPSS rescore
  38. 2026-06-18 17:52 UTCEPSS rescore
  39. 2026-06-17 17:53 UTCEPSS rescore
  40. 2026-06-17 17:53 UTCEPSS rescore
  41. 2026-06-16 17:52 UTCEPSS rescore
  42. 2026-06-15 17:48 UTCEPSS rescore
  43. 2026-06-14 23:18 UTCEPSS rescore
  44. 2026-06-13 23:00 UTCEPSS rescore
  45. 2026-06-12 23:12 UTCEPSS rescore
  46. 2026-06-12 23:12 UTCEPSS rescore
  47. 2026-06-11 14:00 UTCEPSS rescore
  48. 2026-06-10 22:18 UTCEPSS rescore
  49. 2026-06-10 22:18 UTCEPSS rescore
  50. 2026-06-10 13:22 UTCEPSS rescore
  51. 2026-06-08 14:17 UTCEPSS rescore
  52. 2026-06-08 14:17 UTCEPSS rescore
  53. 2026-06-07 15:25 UTCEPSS rescore
  54. 2026-06-07 15:24 UTCEPSS rescore
  55. 2026-06-06 13:47 UTCEPSS rescore
  56. 2026-06-06 13:47 UTCEPSS rescore
  57. 2026-06-06 13:47 UTCEPSS rescore
  58. 2026-06-05 22:47 UTCEPSS rescore
  59. 2026-06-05 06:10 UTCEPSS rescore
  60. 2026-06-05 06:10 UTCEPSS rescore
  61. 2026-06-04 13:12 UTCEPSS rescore
  62. 2026-06-04 13:12 UTCEPSS rescore
  63. 2026-06-04 13:12 UTCEPSS rescore
  64. 2026-06-02 20:13 UTCEPSS rescore
  65. 2026-06-02 20:13 UTCEPSS rescore
  66. 2026-06-01 13:51 UTCEPSS rescore
  67. 2026-06-01 13:51 UTCEPSS rescore
  68. 2026-06-01 13:51 UTCEPSS rescore
  69. 2026-05-31 22:30 UTCEPSS rescore
  70. 2026-05-31 22:30 UTCEPSS rescore
  71. 2026-05-31 00:16 UTCEPSS rescore
  72. 2026-05-31 00:16 UTCEPSS rescore
  73. 2026-05-31 00:16 UTCEPSS rescore
  74. 2026-05-29 15:29 UTCEG score recompute
  75. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-23524?
CVE-2026-23524 is a critical vulnerability published on January 21, 2026. 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…
When was CVE-2026-23524 disclosed?
CVE-2026-23524 was first published in the National Vulnerability Database on January 21, 2026, with the most recent update on March 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23524 actively exploited?
CVE-2026-23524 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 55.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-23524?
CVE-2026-23524 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-23524?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23524, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23524

Explore →

Is Your Infrastructure Affected by CVE-2026-23524?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs