# Post Mortem: Patching the PHP and Node.js Vulnerabilities

DevFeed: [Post Mortem: Patching the PHP and Node.js Vulnerabilities](<https://devfeed.tech/articles/post-mortem-patching-the-php-and-node-js-vulnerabilities-117685.md>)

Original publisher: [Read original article](<https://laravel.com/blog/php-nodejs-vulnerabilities-post-mortem>)

Author: Aaron Francis

Published: 2026-11-04T19:15:00Z

Content type: article

Language: en

Sources: [Laravel Blog](<https://devfeed.tech/sources/laravel-blog.md>)

Topics: [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [PHP](<https://devfeed.tech/topics/php.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [disclosures](<https://devfeed.tech/tags/disclosures.md>), [forge](<https://devfeed.tech/tags/forge.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [patching](<https://devfeed.tech/tags/patching.md>), [php](<https://devfeed.tech/tags/php.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

## AI overview

Laravel Cloud patched every running application in place within about five hours of the PHP release, with no customer action or downtime reported. Its Kubernetes operator installed patched PHP binaries and restarted workloads in paced waves; the team accelerated the restart pacing fivefold, used canaries, and temporarily paused new Cloud deployments. A Cloudflare managed firewall ruleset added protection while the patch was prepared, but the article says it could not replace patching. Building its own PHP image let Laravel ship before Docker Hub's patched images were available. Other products required different responses: Forge customers had to upgrade PHP, and a surge of jobs starved deployments, leading to about 4,800 cancellations; Envoyer went offline for server upgrades; Vapor customers needed to redeploy for new runtimes and images. The team says it is adding recovery soak periods and recorded war rooms, separating Forge's deployment queue, modernizing Envoyer, and reviewing Vapor's redeployment policy.

## Source excerpt

How we patched every Laravel Cloud app in place within about 27 hours of the PHP and Node.js disclosures, what broke on Forge, Envoyer, and Vapor, and what we are changing.