PHP2Shell Vulnerabilities: What You Need to Know

16 November 2026 Storm Technologies
PHP2Shell Vulnerabilities
Two critical vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619, could allow an unauthenticated attacker to execute code on an affected system.
 
Collectively known as PHP2Shell, the vulnerabilities could affect more than public-facing websites. PHP may also be present in internal applications, hosted services, management tools and third-party products, making it important to understand where it is running across your technology estate.
 
The immediate priority is to identify potentially affected systems and apply the appropriate security updates. Organisations should also consider how they will validate their exposure, prioritise remediation and confirm that the required action has been taken.
 
 

What is PHP2Shell?

PHP2Shell is the collective name given to two vulnerabilities affecting the way PHP handles web requests and memory.
 
CVE-2026-109618 relates to how PHP handles an out-of-memory condition. Under certain circumstances, request data may only be partially initialised when PHP begins its clean-up process. This can lead to memory corruption and potentially allow an attacker to execute code remotely.
 
CVE-2026-109619 concerns PHP workers retaining references to memory after it has been released. A later request processed by the same worker may access this stale information before it has been properly reset, creating another potential route to remote code execution.
 
Both vulnerabilities can allow unauthenticated remote code execution with the privileges of the affected web-server account. The practical risk depends on the PHP version, deployment method and configuration of the system.
 
 

Where could the risk exist?

The challenge for many organisations will be identifying everywhere PHP is running. Potential exposure may extend across:
  • Public websites and customer portals
  • Internal business applications
  • Content management and e-commerce platforms
  • Web-based administration tools
  • Hosted and managed services
  • Products or appliances that embed PHP
  • Legacy applications
  • Systems managed by hosting providers, agencies or other suppliers
This means the review should not be limited to your main website. Application owners, development teams, hosting providers and technology suppliers may all need to be involved.
 
 

What should organisations do now?

Identify affected systems

Establish where PHP is being used across public, internal and supplier-managed systems. Record the installed version, application owner, hosting arrangement and business importance of each service.
Apply the appropriate security updates
The PHP Project has released PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12 to address the vulnerabilities. Organisations should upgrade to the appropriate fixed release or apply an equivalent package supplied by their Linux distribution, hosting provider or product manufacturer.
 
PHP 8.1 and earlier are no longer supported by the upstream PHP Project. Organisations using these branches should confirm the availability of an appropriate fix with their distribution or long-term support provider and plan a move to a supported release.
 
 
Validate the outcome
After updating affected systems, confirm that the patched version is installed and active. Where appropriate, complete a targeted exposure assessment and rerun the assessment following remediation. Version information and assessment results should be reviewed together. Servers may hide their PHP version, while suppliers can sometimes backport security fixes without changing the main version string. A clean result also only applies to the systems included within the authorised scope.
Continue monitoring
Review web-server, PHP, proxy and endpoint telemetry for unusual requests, unexpected processes, file changes and other suspicious activity. Web application firewall rules and other temporary measures may help reduce particular attack paths, but they should support rather than replace patching.

How Storm Technologies can help

Understanding your PHP2Shell position requires more than checking one website or running a simple version scan.
 
Storm Technologies can help you identify where further investigation may be needed, define the right scope for an exposure assessment and interpret the findings in the context of your environment.
 
We can also help your teams prioritise affected systems and determine the appropriate next steps across applications, infrastructure and cyber security.
 
 

Concerned about your PHP2Shell exposure?

Speak to a Storm Technologies security specialist. We can help you review the potential risk, identify where further investigation is required and agree the most appropriate next steps.