PHP Vulnerability, Oh My!

Tonight I was working on upgrading a few things across my server infrastructure and ran into an issue that required dropping everything to patch immediately. A massive critical vulnerability dropped for the core PHP engine (specifically CVE-2026-109618 and CVE-2026-109619), which allows unauthenticated remote code execution (RCE). If you host your own VPS or dedicated boxes running WordPress, Laravel, or anything else on PHP, you need to look at this today. [1] (https://flaviocopes.com/php-security-update/), [2] (https://www.computing.co.uk/news/2026/security/php-emergency-patches-for-critical-flaws), [3] (https://www.therepository.email/exploit-claims-surface-ahead-of-critical-php-security-release-as-wordpress-hosts-scramble), [4] (https://ramblingman.info/tag/aws/)
Here is a quick look at how I handled the OS package updates, verified my environments, and remediated the PHP bugs. [1] (https://www.computing.co.uk/news/2026/security/php-emergency-patches-for-critical-flaws)

Prepping the OS Packages

First, let’s look at the underlying OS. I prefer pulling the updated downstream packages directly from the Linux distribution repositories rather than compiling from source, as long-term support (LTS) distros backport critical security patches into their stable versions.
One thing to watch out for: don’t just rely on php -v in the command line. Your CLI runtime might show one version, while your active web server workers (like PHP-FPM or Apache) are actually executing code on an unpatched binary. [1] (https://flaviocopes.com/php-security-update/)
Let’s check the cert setup and prepare to restart the pools: [1] (https://ramblingman.info/2021/11/01/using-haproxy-as-a-front-end-ssl-terminator-for-sonar-qube/)

ramblingman@webserver:~$ php -v
ramblingman@webserver:~$ sudo apt-get update && sudo apt-get --only-upgrade install php*-cli
ramblingman@webserver:~$ a2dismod php7.4
ramblingman@webserver:~$ a2enmod php8.4

Targeting the Right Versions

To fully remediate the “PHP2Shell” memory corruption flaws, you need to ensure your active environment matches or exceeds these specific point-releases: [1] (https://www.computing.co.uk/news/2026/security/php-emergency-patches-for-critical-flaws)

In my case, the PHP system is 8.4.27.

Hardening via FPM Configurations

If you have a couple of staging sites or complex environments where you can’t update the point-releases immediately, you can inject some mitigations directly into your PHP-FPM pool files using php_admin_value so individual application code can’t accidentally override them.
I modified my configuration files to explicitly disable the session upload progress feature and tweak the memory boundaries:

; Temporary mitigation for CVE-2026-109618 / 109619
session.upload_progress.enabled = 0
memory_limit = -1

Once the configuration changes are saved, you must cycle your worker processes to flush the old instructions out of active system memory: [1] (https://www.computing.co.uk/news/2026/security/php-emergency-patches-for-critical-flaws)

ramblingman@webserver:$ sudo systemctl restart apache2

The WordPress Layer

With the base server secured, I turned my attention to the application layer. Keep in mind that updating your WordPress core or your plugins will not fix this issue. The flaw exists entirely in the PHP binary itself. However, changing your server’s runtime configuration can break old templates, so it’s a good time to run standard site updates. [1] (https://wordpress.org/news/2026/10/critical-php-security-release/), [2] (https://www.therepository.email/exploit-claims-surface-ahead-of-critical-php-security-release-as-wordpress-hosts-scramble)
I logged into the dashboard to verify everything was clean. You can check your absolute runtime environment by navigating to Tools > Site Health > Info > Server. [1] (https://www.searchenginejournal.com/critical-php-core-security-flaws-affect-websites-including-wordpress/593812/), [2] (https://wordpress.org/news/2026/10/critical-php-security-release/)
This panel will explicitly tell you which version of PHP your live web request process is running on. If you see something like 8.3.36 or higher, the patch is successfully processing your site traffic. [1] (https://wordpress.org/news/2026/10/critical-php-security-release/), [2] (https://www.searchenginejournal.com/critical-php-core-security-flaws-affect-websites-including-wordpress/593812/), [3] (https://www.computing.co.uk/news/2026/security/php-emergency-patches-for-critical-flaws)

Hopefully this helps someone out there, stay vigilant!