Table of Contents
ToggleOn October 21, 2026, the PHP project released emergency security updates for two critical vulnerabilities: CVE-2026-109618 and CVE-2026-109619. Both carry a CVSS v4.0 score of 9.2 and can allow an unauthenticated attacker to execute code through vulnerable PHP web deployments.
If you operate a PHP website, hosting server, or billing platform, identify the runtime serving each application and install a verified patched build promptly. Updating website plugins alone does not repair the PHP runtime.
Advisory checked: October 22, 2026. The release date is October 21. The official PHP security announcement provides the primary remediation guidance.

Which PHP Versions Contain the Fixes?
The upstream security releases are:
| PHP branch | Fixed upstream release |
|---|---|
| PHP 8.2 | 8.2.35 |
| PHP 8.3 | 8.3.36 |
| PHP 8.4 | 8.4.27 |
| PHP 8.5 | 8.5.12 |
Install the fixed release for your branch or a later patched release. The official PHP downloads page lists current releases.
Distribution packages may contain backported fixes while retaining an older upstream version number. Verify the complete package revision against your vendor advisory.
For example, Ubuntu security notice USN-8948-1 lists patched packages including PHP 8.3.6-0ubuntu0.24.04.13 for Ubuntu 24.04 LTS and PHP 8.1.2-1ubuntu2.28 for Ubuntu 22.04 LTS. Those vendor revisions matter; the leading PHP version alone cannot establish patch status.
PHP 8.1 and older lack routine upstream support. Obtain explicit confirmation of vendor fixes or plan migration to a supported branch. Exceptional source backports do not restore normal support.
What Do These Vulnerabilities Do?
CVE-2026-109618: Out-of-Memory Corruption
PHP can enter an unsafe cleanup path after memory allocation fails while request data is only partially initialized.
The PHP project’s OOM corruption advisory documents unauthenticated remote code execution against Apache mod_php, including a path triggered before application code runs. Successful execution occurs with the web worker’s privileges; it does not automatically mean root access.
CVE-2026-109619: Stale State Between Requests
A persistent worker can retain references to memory belonging to a completed request. A later request can encounter that stale state.
The PHP project’s stale global state advisory describes several paths involving errors, configuration processing, and session upload progress. Reachability varies with the PHP version, handler, application, and extensions.
Administrators should prioritize exposed deployments without assuming every environment has identical exploit conditions.
Are WordPress and WHMCS Affected?
These are PHP runtime vulnerabilities. WordPress, WHMCS, Magento, custom applications, and other PHP software need their underlying runtime checked.
The WordPress security announcement explicitly says that no WordPress update is required or planned for these issues. Within WordPress, check Tools → Site Health → Info → Server to identify the website’s PHP version.
For WHMCS, inventory both the web runtime and the PHP binary used by scheduled tasks. Confirm compatibility with the installed WHMCS version, ionCube Loader, and third-party modules before changing PHP branches. A security patch within the existing supported branch is usually a smaller compatibility change than a major upgrade.
Keep updating applications through their normal channels, but verify PHP separately.
Step 1: Identify Every PHP Runtime
Start with the command-line binary:
command -v php
php -v
php --ini
These commands inspect the selected CLI runtime. A website may use another PHP version, configuration file, or handler.
List running PHP-related processes and service units:
ps -eo pid,user,args | grep -E '[p]hp-fpm|[l]sphp|[f]rankenphp'
systemctl list-units --type=service --all | grep -Ei 'php|apache|httpd|lsws'
Check every domain’s handler in the hosting panel. Also inventory container images, separate FPM pools, cron entries, application workers, and secondary servers.
If terminal administration is unfamiliar, our guide to Linux commands for hosting administrators explains useful inspection commands.
Step 2: Establish Who Supplies PHP
Updates must come through the installation’s package or build system:
- Operating-system packages: use that distribution’s security repository.
- cPanel EasyApache: update the installed EasyApache PHP packages.
- CloudLinux or another alternate PHP provider: check each provider’s advisory.
- DirectAdmin or Plesk: use the panel’s supported PHP update process.
- Containers: rebuild and redeploy using a patched image.
- Source installations: rebuild from the appropriate patched source release.
Our explanation of hosting control panels and their management layers helps distinguish the panel from the runtime it manages.
For shared hosting accounts, ask the provider to confirm the patched build serving your domain. Switching a version selector is sufficient only if the selected runtime is actually patched.
Step 3: Apply the Correct Package Update
Take a current recoverable backup and record the installed package revisions. Keep the existing branch where a suitable security fix is available.
On a plain Debian or Ubuntu installation, inspect PHP packages and refresh repository information:
dpkg-query -W 'php*' 'libapache2-mod-php*'
sudo apt update
apt-cache policy php8.3-fpm php8.3-cli php8.3-common
For a server using distribution-provided PHP 8.3 FPM, an example update is:
sudo apt install --only-upgrade php8.3-fpm php8.3-cli php8.3-common
Replace the branch and package list with the installed runtime and extensions. This example does not update cPanel’s ea-php, alternate vendor packages, or container images.
On an RPM-based server, inspect the actual package names first:
rpm -qa | grep -Ei '^(php|ea-php|alt-php)'
dnf check-update
Apply the update command recommended by the package vendor.
For cPanel, its official system update instructions direct administrators to WHM’s EasyApache 4 interface for Apache PHP updates. Update every affected installed branch and confirm package availability; updating the panel alone is insufficient evidence.
On dedicated servers with administrative access, document who owns runtime updates, particularly when operating several application stacks.
Step 4: Restart the Affected Workers
An updated file on disk does not prove that every running process has replaced its old code.
Identify the actual service and restart it through the distribution or panel’s supported procedure. For a standard PHP 8.3 FPM service, for example:
sudo php-fpm8.3 -t
sudo systemctl restart php8.3-fpm
sudo systemctl status php8.3-fpm --no-pager
Executable names and service units vary. Apache mod_php deployments require replacement of the affected Apache workers. LiteSpeed, FrankenPHP, and container deployments have their own restart or redeployment procedures.
Account for every pool and worker. Restarting NGINX alone does not replace a separate PHP-FPM process.
Step 5: Verify the Application Runtime
After updating:
- Match installed package revisions against the vendor advisory.
- Confirm the PHP version serving each website.
- Confirm all affected workers were replaced.
- Test logins, forms, uploads, checkout, and scheduled jobs.
- Inspect service and application logs.
Example checks:
php -v
sudo journalctl -u php8.3-fpm --since "15 minutes ago" --no-pager
curl -I https://example.com/
A successful HTTP response tests availability; it does not establish patch status. Likewise, a patched CLI binary does not establish that a website uses the same runtime.
Use an authenticated administrative view where possible. Avoid leaving public phpinfo() pages online.
Does Cloudflare Remove the Need to Update?
Cloudflare reports deploying WAF protections for these vulnerabilities and observing attack traffic. Its PHP vulnerability protection announcement still advises customers to patch PHP.
Keep applicable protections enabled, check for bypass rules, and consider whether an attacker can reach the origin directly. WAF coverage reduces exposure; it does not replace the vulnerable runtime.
What If You Cannot Patch Immediately?
PHP’s advisory includes temporary measures for specific attack paths, but they do not provide complete protection.
For example, disabling session.upload_progress.enabled before request parsing and restarting all workers blocks confirmed session-related paths for CVE-2026-109619. It does not address every variant or the separate OOM issue.
Other recommendations involve request limits and memory-management settings. Read the complete advisory with your administrator before applying them: changing memory limits affects availability, and application-level settings may take effect too late.
If a verified fix cannot be deployed promptly, assess temporarily restricting or withdrawing the exposed service while remediation proceeds.
For help identifying runtimes, coordinating updates, and checking applications afterward, review our server management services. Confirm the work covered by the selected plan.
What Should Administrators Do Now?
Inventory every web-facing PHP installation, install an upstream fix or vendor-confirmed backport, replace affected workers, and verify each application.
If logs or file changes suggest compromise, patching alone is insufficient. Preserve evidence and investigate the incident.
Record the package revisions, restart time, and verification results. That record provides a stronger basis for confirming remediation than an update notification or a version number from one terminal.



