Skip to content

🚨 [security] [php] Update laravel/reverb 1.5.1 → 1.7.1 (minor)#55

Closed
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/composer/laravel/reverb-1.7.1
Closed

🚨 [security] [php] Update laravel/reverb 1.5.1 → 1.7.1 (minor)#55
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/composer/laravel/reverb-1.7.1

Conversation

@depfu
Copy link

@depfu depfu bot commented Feb 7, 2026


Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!



🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!


Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ laravel/reverb (1.5.1 → 1.7.1) · Repo · Changelog

Security Advisories 🚨

🚨 Laravel Redis Horizontal Scaling Insecure Deserialization

Impact

This vulnerability affects Laravel Reverb versions prior to v1.7.0 when horizontal scaling is enabled (REVERB_SCALING_ENABLED=true).

The exploitability of this vulnerability is increased because Redis servers are commonly deployed without authentication.

With horizontal scaling enabled, Reverb servers communicate via Redis PubSub. Reverb previously passed data from the Redis channel directly into PHP’s unserialize() function without restricting which classes could be instantiated.

Risk: Remote Code Execution (RCE)

Patches

This vulnerability is fixed in Laravel Reverb v1.7.0.

Update your dependency to laravel/reverb: ^1.7.0 immediately.

Workarounds

If you cannot upgrade to v1.7.0, you should apply the following mitigations:

  • Redis Security: Require a strong password for Redis access and ensure the service is only accessible via a private network or local loopback.
  • Disable Scaling: If your environment uses only one Reverb node, set REVERB_SCALING_ENABLED=false to bypass the vulnerable logic entirely.

Credits

This vulnerability was discovered and responsibly reported by Mohammad Yaser Abo-Elmaaty @m0h4mmad

Release Notes

1.7.1

1.7.0

1.6.3

1.6.2

1.6.1

  • Decode the client event data if it is a valid json string by @vunguyen-it in #352

1.6.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 17 commits:


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu
Copy link
Author

depfu bot commented Feb 28, 2026

Closed in favor of #64.

@depfu depfu bot closed this Feb 28, 2026
@depfu depfu bot deleted the depfu/update/composer/laravel/reverb-1.7.1 branch February 28, 2026 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants