- October 22, 2026
- 50
- No Comments
Urgent PHP Security Update Needed on Your Server (CVE-2026-109618 / CVE-2026-109619)
Published: 22 October 2026 | Category: Cybersecurity & Server Management
Two critical PHP security vulnerabilities have been discovered, putting websites, applications, and servers worldwide at risk of remote code execution (RCE). On 21 October 2026, the PHP development team released emergency security updates addressing these vulnerabilities, identified as CVE-2026-109618 and CVE-2026-109619.
Both vulnerabilities carry a critical severity rating of 9.2 under the CVSS v4.0 scoring system and can potentially allow unauthenticated attackers to execute malicious code on vulnerable servers. Reports of active exploitation make this an urgent security issue for website owners, developers, hosting providers, and server administrators.
If your website or application runs on PHP, you should immediately check your installed version and apply the appropriate security patches.
What Happened? Understanding the Critical PHP Security Vulnerabilities
PHP powers millions of websites and web applications, including platforms built with WordPress, Laravel, Drupal, Magento, and other PHP-based technologies.
On 21 October 2026, the PHP security team published an official advisory describing two vulnerabilities affecting PHP installations that process web requests.
These vulnerabilities involve memory handling and internal application state management within PHP. Under certain conditions, attackers may be able to manipulate how PHP handles requests, potentially achieving remote code execution without authentication.
Successful exploitation could allow an attacker to execute commands under the permissions of the affected web server or PHP worker account.
Depending on server configuration and permissions, an attack could result in:
Unauthorized access to website files and application data.
Modification or deletion of website content.
Exposure of sensitive configuration information.
Installation of malicious scripts or backdoors.
Compromise of applications hosted on the affected server.
Further attacks against connected systems or services.
The PHP project has strongly recommended immediate updates because there is no complete workaround that eliminates these vulnerabilities without patching.
The Two Critical PHP Vulnerabilities Explained
1. CVE-2026-109618: Remote Code Execution via Out-of-Memory Corruption
Severity: Critical — CVSS v4.0 Score: 9.2
This vulnerability is associated with PHP’s handling of out-of-memory conditions.
When memory allocation fails during certain request-processing operations, internal PHP data structures may remain partially initialized. Subsequent cleanup operations can incorrectly interpret this incomplete data as valid, resulting in memory corruption.
Under exploitable conditions, attackers may manipulate this behavior to execute unauthorized code.
Potential impact:
Memory corruption during PHP request processing.
Remote code execution without authentication.
Compromise of vulnerable PHP worker processes.
Potential exposure of hosted applications and sensitive information.
Official advisory: CVE-2026-109618 – PHP GitHub Security Advisory
2. CVE-2026-109619: Remote Code Execution via Stale Global State
Severity: Critical — CVSS v4.0 Score: 9.2
The second vulnerability involves PHP retaining internal global state that refers to memory already released after processing a request.
Under certain circumstances, this outdated state can be accessed during subsequent operations, causing a use-after-free condition.
An attacker who can influence memory allocation and request processing may be able to exploit this behavior to execute malicious code.
Potential impact:
Unauthorized code execution.
Application instability or unexpected crashes.
Manipulation of PHP worker memory.
Compromise of applications served by affected PHP processes.
Official advisory: CVE-2026-109619 – PHP GitHub Security Advisory
Which PHP Servers and Websites Are Affected?
These vulnerabilities affect vulnerable PHP installations that process web requests. Administrators using the following PHP execution environments should review their installations immediately:
PHP-FPM: Commonly used with Nginx and Apache web servers.
Apache with mod_php: Considered particularly high risk because successful exploitation has been demonstrated in this environment.
PHP-CGI: Used by certain hosting and web server configurations.
FrankenPHP: A modern PHP application server.
LiteSpeed: Commonly deployed in shared hosting and performance-optimized hosting environments.
Websites developed using WordPress, Laravel, Drupal, Magento, and custom PHP frameworks may be exposed when deployed on affected PHP runtime versions.
Important: Updating WordPress, Laravel, plugins, or application code alone does not fix vulnerabilities in the underlying PHP interpreter. The PHP runtime itself must be patched.
Fixed PHP Versions Released on 21 October 2026
The PHP development team has released security patches for the following maintained versions:
| PHP Branch | Fixed Version | Recommended Action |
|---|---|---|
| PHP 8.5 | 8.5.12 | Update immediately |
| PHP 8.4 | 8.4.27 | Update immediately |
| PHP 8.3 | 8.3.36 | Update immediately |
| PHP 8.2 | 8.2.35 | Update and plan migration |
| PHP 8.1 and older | No current upstream security release | Upgrade or obtain a supported vendor backport |
PHP 8.2 is scheduled to reach end of life on 31 December 2026. Organizations still running PHP 8.2 should begin planning their migration to a newer supported PHP version.
PHP 8.1 and older versions no longer receive regular security updates directly from the PHP project. Some hosting vendors provide security backports for older branches, but administrators should verify that these packages specifically address both CVEs.
Official source: PHP Security Release Announcement – 21 October 2026
How to Protect Your Server from These PHP Vulnerabilities
Taking immediate action can significantly reduce the likelihood of a successful attack.
Follow these essential steps to protect your server and hosted applications.
Step 1: Back Up Your Website and Server
Before installing updates, create a complete backup of your server or hosting environment.
Your backup should include:
Website files and application directories.
MySQL, MariaDB, or other application databases.
PHP configuration files.
Web server configuration.
SSL certificates and relevant service settings.
Critical application and hosting configurations.
For VPS, VDS, and dedicated servers, consider creating a server snapshot through your hosting provider.
Verify that your backup is accessible and can be restored if necessary.
Step 2: Identify Your Current PHP Version
If you have SSH access, check your server’s default command-line PHP version:
php -vExample output:
PHP 8.3.36 (cli)However, the PHP version shown by the command line may differ from the PHP version used by your website.
Administrators using cPanel, Plesk, or multiple PHP installations should verify every installed and active PHP version.
On cPanel servers, you can review PHP installations using EasyApache 4 and MultiPHP Manager.
Do not assume your website is protected simply because the command-line version has been updated.
Step 3: Install the Latest PHP Security Updates
Update your server to a patched PHP version through the appropriate package manager or hosting control panel.
Depending on your hosting environment, this may involve:
Running system package updates through your Linux distribution.
Updating PHP packages through WHM or cPanel.
Installing available updates through Plesk.
Updating PHP packages provided by CloudLinux.
Updating application containers or custom PHP runtime installations.
Use official or trusted vendor-maintained packages wherever possible.
Before making major version changes, review application and extension compatibility.
Step 4: Restart PHP-FPM, Apache, or Your Web Server
Installing updated packages is not always enough.
Existing PHP worker processes may continue running previously loaded code until they are restarted.
After installing security updates, restart the PHP processing services used by your websites.
These may include:
PHP-FPM services.
Apache HTTP Server.
LiteSpeed or other PHP-serving processes.
Application containers with embedded PHP runtimes.
The exact restart command depends on the server configuration and PHP installation method.
Restarting the relevant services is essential to ensure that PHP workers load the patched code.
Step 5: Verify That the Patched PHP Version Is Running
After completing the update, confirm that your website is using a fixed PHP version or a vendor-confirmed patched build.
Check the PHP command-line version:
php -vThen independently confirm the PHP runtime used to serve web requests.
A temporary PHP information page can help identify the active web PHP version. If you use this method, restrict access and remove the file immediately after verification because it may expose sensitive server configuration information.
On servers hosting multiple websites or PHP versions, repeat this verification for every active PHP environment.
How to Update PHP in cPanel and WHM
If you manage websites through cPanel and WHM, security updates for EasyApache 4 are available.
cPanel confirmed patched PHP packages for the affected branches in its 21 October 2026 security announcement.
Recommended procedure:
Sign in to WHM as an administrator.
Open Upgrade to Latest Version or the relevant update interface.
Review available cPanel and EasyApache updates.
Install the latest vendor-provided security patches.
Confirm the PHP versions installed through EasyApache 4.
Restart the relevant PHP-FPM and Apache services if necessary.
Verify the PHP versions actually serving your websites.
Administrators with root SSH access may use:
/scripts/upcpFor updating EasyApache PHP RPM packages specifically, cPanel also documents:
/scripts/rpmupCheck your server’s configuration and current vendor instructions before running updates.
For more information, review the official cPanel PHP security announcement.
How to Update PHP in Plesk
Website owners and server administrators using Plesk should install the latest available Plesk Obsidian updates and PHP packages.
To check for updates:
Sign in to your Plesk control panel.
Navigate to Tools & Settings.
Open Updates or Updates and Upgrades, depending on the version.
Install the relevant PHP security updates.
Restart affected PHP services.
Confirm each hosted website is running a patched version.
Administrators should consult official Plesk release information for package availability and instructions specific to their environment.
CloudLinux and Older PHP Versions
Servers running CloudLinux may use Alt-PHP or other vendor-supported PHP packages.
Administrators should verify security patch availability through the official CloudLinux channels and confirm that the installed packages address both vulnerabilities.
CloudLinux and other vendors may provide extended lifecycle security patches for older PHP releases.
However, an older PHP version number does not automatically mean a vendor-maintained build remains vulnerable. Backported patches may retain the original PHP branch version number.
The important consideration is whether the installed vendor package contains the required security fixes.
Visit the CloudLinux status page for relevant announcements.
What If You Cannot Update PHP Immediately?
Some organizations may not be able to update PHP immediately because of application compatibility requirements, dependency conflicts, or unavailable vendor packages.
In these situations, administrators should consult the official PHP security advisory for temporary risk-reduction measures.
Additional precautions may include:
Restricting public access to applications that do not need to be internet-facing.
Enforcing appropriate network and access controls.
Monitoring web server requests and application errors.
Reviewing PHP process behavior and resource consumption.
Increasing monitoring for suspicious activity.
A web application firewall may provide additional protection, but it cannot be relied upon to eliminate these memory-safety vulnerabilities.
Temporary mitigations are not a complete fix. Installing patched PHP packages remains the recommended solution.
PHP Server Security Best Practices
Beyond these critical vulnerabilities, maintaining a secure PHP hosting environment requires continuous monitoring and maintenance.
Keep PHP and Server Packages Updated
Apply security patches promptly and regularly review official vendor advisories.
Where suitable, enable automatic security updates through your operating system or hosting control panel.
Remove Unused PHP Versions
Older, unused PHP installations can increase the attack surface.
Review installed PHP packages and remove unsupported branches that are no longer required by hosted applications.
Update CMS Platforms, Plugins, and Frameworks
Keep WordPress, Laravel, Drupal, Magento, plugins, themes, and third-party dependencies updated.
Even when the underlying PHP environment is secure, outdated application components can introduce additional vulnerabilities.
Strengthen Administrative Access
Protect SSH, WHM, cPanel, Plesk, and application administration interfaces using strong authentication, multi-factor authentication, and appropriate access restrictions.
Avoid exposing sensitive management interfaces unnecessarily.
Monitor for Signs of Server Compromise
Server administrators should monitor for unusual activity, including:
Unexpected PHP files appearing in website directories.
Unauthorized file modifications.
Unknown cron jobs or scheduled tasks.
Suspicious background processes.
Unusual spikes in CPU or memory usage.
Unexpected outgoing network traffic.
Unrecognized administrator accounts.
If compromise is suspected, investigate promptly, preserve relevant logs, and consider isolating affected services.
Installing the security update prevents exploitation through the patched vulnerabilities, but it does not automatically remove malware or reverse damage from an earlier compromise.
Frequently Asked Questions
What is CVE-2026-109618?
CVE-2026-109618 is a critical PHP vulnerability involving memory corruption during out-of-memory handling. Under exploitable conditions, it can enable unauthenticated remote code execution.
What is CVE-2026-109619?
CVE-2026-109619 is a critical PHP vulnerability involving stale global state and use-after-free behavior. Attackers may exploit affected installations to execute unauthorized code.
Are WordPress websites affected?
WordPress websites running on vulnerable PHP installations may be exposed. Updating WordPress itself does not resolve the underlying PHP vulnerabilities. The server’s PHP runtime must be patched.
Are Laravel applications affected?
Laravel applications using vulnerable PHP versions may also be exposed because these are PHP runtime vulnerabilities rather than vulnerabilities in the Laravel framework itself.
Is PHP-FPM affected?
Yes. PHP-FPM is included among the affected PHP execution environments. Administrators should apply security updates regardless of whether they use PHP-FPM, mod_php, or another supported web-facing configuration.
Can a firewall protect my server without updating PHP?
A firewall can help reduce certain attack opportunities, but it does not eliminate the vulnerabilities. Applying the appropriate PHP security updates is essential.
Do I need to restart my server after updating PHP?
A full server reboot is not always necessary. However, affected PHP-FPM, Apache, or other PHP-serving processes must be restarted or replaced to load the patched code.
Which PHP version should I install?
Install the latest fixed release available for your supported PHP branch, or a vendor-confirmed package containing the backported fixes. For the 21 October 2026 release, the upstream fixed versions are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35.
Final Thoughts: Update Your PHP Server Immediately
The discovery of CVE-2026-109618 and CVE-2026-109619 highlights the importance of maintaining secure, updated server environments.
With both vulnerabilities rated critical and capable of allowing unauthenticated remote code execution, website owners and system administrators should treat these updates as an immediate priority.
Whether your websites run on WordPress, Laravel, or custom PHP applications, the responsibility remains the same: identify vulnerable installations, install verified security patches, restart the affected services, and confirm the updated versions are running.
Do not delay critical PHP security updates. Protect your website, application data, and server infrastructure today.
Need Help Securing Your PHP Server?
If you are unsure which PHP version your website uses or need assistance updating your hosting environment, contact your web hosting provider or an experienced server administrator.
Professional server maintenance, security audits, and timely patch management can help prevent vulnerabilities from becoming serious security incidents.
Take action today to keep your website and server secure.
