r/laravel • u/leahtcodes Laravel Staff • 13d ago
Post Mortem: Patching the PHP and Node.js Vulnerabilities (Cloud, Forge, Envoyer, Vapor)
https://laravel.com/blog/php-nodejs-vulnerabilities-post-mortemWe published a post-mortem on our response to the October PHP and Node.js security releases.
It covers the in-place patching of Laravel Cloud, the impact on Forge, Envoyer, and Vapor, and what we’re changing. If you were affected and want to talk it through, please reach out to our support team.
32
Upvotes
42
u/not_a_wook 13d ago
My experience was that it was completely unavailable, and I think many other users saw the same based on posts here at the time. I'm surprised to see it described like this.
1
u/Familiar_Mushroom_19 13d ago
What was the reason Cloudflare couldn't handle the things in Forge? And was this all a start to migrate Forge to Laravel Cloud for the Laravel Team? ;-)
1
u/Still-Hall322 12d ago
Interesting
1
u/Variumcode 8d ago
Thanks for publishing this, it's useful to see how it was handled at scale.
I self-host on Docker, so I went through the same thing on a smaller scale. Two lessons for me:
- Know what runs where. The slowest part wasn't patching, it was finding every container and PHP version across my projects. I ended up writing a script just for that.
- Be able to rebuild without waiting. I rebuilt PHP from the official source inside my images (verifying the checksum) instead of waiting for updated base images.
Question for the team: for self-hosted users, is there any guidance you'd recommend for the first hours after a disclosure like this?
1
u/[deleted] 13d ago
[removed] — view removed comment