Le correctifs des failles critiques de PHP sont tellement attendu que la site officiel https://t.co/hsVhlWzJhW subit un afflux massif de consultation le rendant instable, vous pouvez avoir un coup la page, ou un timeout.
Courage à tous les admin qui vont faire des heures sup'
PHP just shipped fixes for two critical RCE bugs (CVE-2026-109618 / 109619). 8.4.27 hit https://t.co/acnUjtGImf at 13:36 UTC, ahead of the announced 14:00.
On Laravel Forge nothing patches itself. Here's how I prepped my server, and what caught me off guard 🧵
1. Check your starting point.
php -v
apt-cache policy php8.4-fpm
Mine was on 8.4.16, ten patch releases behind.
Fixes only ship for PHP 8.2+. On 8.1 or older, plan an upgrade or take the site offline.
2. A https://t.co/acnUjtGImf release doesn't mean you can install it yet.
Forge installs PHP from Ondřej Surý's PPA. As I write this, the PPA has no 8.4.27 build, and its CDN is throwing 503s under load.
Check what your server can actually get:
sudo apt-get update
apt-cache policy php8.4-fpm
3. Stopgap #1: turn off upload progress. It's unofficial but low risk for Laravel apps.
Add to your PHP-FPM pool config:
php_admin_flag[session.upload_progress.enabled] = off
Then restart PHP-FPM.
4. Verify it's actually live.
Forge saved my pool config instantly, but the FPM restart sat in its queue for ~10 minutes.
php -i won't help, since the CLI doesn't read pool settings. Check the FPM master restarted:
ps -o lstart= -C php-fpm8.4
5. Stopgap #2: block multipart requests in nginx. It breaks uploads until you remove it.
On Forge, each site includes forge-conf/<site-id>/server/* inside its server block, so one file per site covers all its domains:
if ($http_content_type ~* "multipart") { return 403; }
6. Expect Forge's queue to be slammed when everyone hits "Update PHP" at once.
Keep an SSH + sudo fallback ready:
sudo apt-get update
sudo apt-get install --only-upgrade $(dpkg -l 'php8.4-*' | awk '/^ii/{print $2}')
sudo systemctl restart php8.4-fpm
7. Restart everything that holds PHP in memory, not just FPM:
• Queues: php artisan queue:restart
• Horizon: php artisan horizon:terminate
• Octane: restart the daemon itself (octane:reload keeps the old binary)
8. After patching:
• php-fpm8.4 -v shows the new version
• FPM master start time is after the update
• Every site still returns 200
• Remove the multipart block and confirm uploads work again
9. Don't rely on these:
• file_uploads = Off or a tiny post_max_size. PHP has already parsed the request by then.
• On Apache, don't just disable the PHP handler. It'll serve your .php source as plain text, secrets and all.
10. Once patched, check for signs of compromise: php-fpm spawning shells or download tools, unknown files in public/, new cron jobs, new users.
Crypto People just keep sending me SOL
I have no idea whats going on but Im glad people are excited about Embryo corp creating the next generation of animals
@josiezayner 9D99UtHw3FjFXwURJgGrXVs4HWNC1qj3HMuYz8BTBr3h
this was your wallet address correct?
I saw you moved the money to a secure spot already so it would be great to know if we keep supporting this wallet!