software

Critical PHP Security Flaws Allow Remote Code Execution; Developers Urged to Patch Immediately

Two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, could expose web servers to remote code execution. Check affected versions and install the security updates released on October 21, 2026.

By Srinivas ·

Critical PHP Security Flaws Allow Remote Code Execution; Developers Urged to Patch Immediately
Two critical vulnerabilities in PHP could expose internet-facing web servers to remote code execution, prompting urgent security updates for supported versions of the programming language.

Website operators and software developers have been urged to update their PHP installations immediately after the discovery of two critical security vulnerabilities that could allow attackers to execute malicious code on vulnerable servers without authentication.

The vulnerabilities, identified as CVE-2026-109618 and CVE-2026-109619, affect PHP’s core runtime, the software responsible for executing PHP code on web servers. Both flaws carry a severity score of 9.2 out of 10 under the Common Vulnerability Scoring System (CVSS) 4.0, placing them in the critical category.

The security issues, collectively referred to as PHP2Shell, are particularly concerning because an attacker may be able to exploit vulnerable server configurations without first obtaining a legitimate account or logging in to the application. Successful exploitation could provide a route to remote code execution, potentially allowing an attacker to run unauthorised commands, interfere with applications or compromise data accessible to the affected service. The flaws may also expose sensitive information held in PHP process memory.

The first vulnerability, CVE-2026-109618, involves PHP’s handling of memory exhaustion. Under certain conditions, an out-of-memory event can interrupt request processing before internal data structures have been fully initialised. Subsequent cleanup operations may then handle invalid data in an unsafe way.

The second issue, CVE-2026-109619, involves stale internal state that can remain after the memory associated with a request has been released. A later request handled by the same worker may encounter that state before the runtime has properly reset it, creating an opportunity for exploitation.

These weaknesses are present in the PHP runtime rather than being limited to a particular website, content management system or application plugin. Consequently, applications built with PHP may be exposed even when their own source code does not contain the underlying defect.

The potential exposure extends to different ways of running PHP, including PHP-FPM, Apache configurations using mod_php, php-cgi, FrankenPHP and LiteSpeed. The PHP security team has identified configurations using Apache’s mod_php as particularly concerning because a demonstrated attack can reach the vulnerable code before the application itself begins processing the request.

In response, the PHP development team released security updates on October 21. Administrators using the current supported release branches should upgrade to PHP 8.5.12, PHP 8.4.27, PHP 8.3.36 or PHP 8.2.35, depending on the branch their applications use. Each of these releases addresses both vulnerabilities.

Systems running PHP 8.1 or older versions require additional attention. These branches no longer receive security fixes directly from the PHP project, although some operating-system distributions and long-term-support vendors may provide backported patches. Administrators should confirm the status of their specific package with the relevant vendor rather than assuming that an older installation is protected.

The urgency extends beyond large enterprises. Hosting providers, e-commerce platforms, content management systems, small business websites and self-managed servers may all depend on PHP, sometimes through software bundled by a third-party provider. Updating the main website application alone will not necessarily fix the issue if an affected PHP runtime remains in use elsewhere in the infrastructure.

Security authorities have advised organisations to identify every exposed PHP installation, prioritise systems accessible from the public internet and apply the appropriate patches. A proof-of-concept exploit has also been reported publicly, increasing the importance of prompt remediation. At the time of the Canadian Centre for Cyber Security’s October 21 advisory, it reported no identified active exploitation; that assessment could change as attackers examine the vulnerabilities and develop their own methods.

Where immediate patching is not possible, organisations should consider temporarily isolating exposed applications from public networks while remediation is prepared. Additional protective controls can reduce exposure in specific configurations, but the PHP project has warned that there is no complete substitute for installing the security updates.

After patching, administrators should verify the PHP version actually running in production, rebuild and redeploy affected containers where necessary, restart services as required, and review web-server and application logs for unusual requests or unexpected processes. Security teams should also check third-party appliances and hosting environments, since some products include PHP without making that dependency obvious to the operator.

The incident also highlights a growing role for artificial intelligence in security research. Researchers involved in identifying and analysing the vulnerabilities used AI-assisted techniques as part of the investigation and remediation process. That contribution illustrates how such tools can support defensive security work, but it does not remove the need for independent testing, careful disclosure and timely patching.

PHP remains an important component of the web infrastructure supporting dynamic websites and applications. These vulnerabilities demonstrate how defects deep inside a widely deployed runtime can affect systems across multiple industries, regardless of the framework or application built on top of it.

For website owners and developers, the immediate priority is clear: establish which PHP versions are running, apply the appropriate security update and verify that all exposed environments have been remediated. Delaying the update leaves an avoidable security risk in place at a time when technical details and exploit code can make vulnerable systems easier to target.