PHP2Shell: Your Website May Need an Emergency PHP Update
The page still loads. That does not mean the software behind it is safe.
A website can look perfectly healthy while the software underneath it needs an emergency repair. That is the practical problem behind PHP2Shell: two critical flaws in the PHP runtime, a component many website owners never manage directly.
What happened?
On October 21, 2026, PHP released emergency security updates. The two vulnerabilities can allow remote code execution without authentication: an attacker may be able to make the server execute code without first logging in. PHP's advance notice rated both issues 9.2 under CVSS v4.0. [1]
CVE-2026-109618 concerns memory handling when a request runs out of memory. Interrupted initialization can leave invalid internal data for cleanup routines to process. CVE-2026-109619 concerns internal state surviving after the memory behind it has been freed, creating a dangerous situation for subsequent processing. [2] [3]
Who needs to pay attention?
PHP identifies web-serving installations across Apache with mod_php, PHP-FPM, php-cgi, FrankenPHP and LiteSpeed as at risk. Its highest stated risk is mod_php, where a demonstrated attack reaches PHP before application code runs. [1]
Risk still depends on deployment. Red Hat reports that its default PHP-FPM setup on RHEL 8 and later makes practical remote code execution harder; that is a reason to consult the vendor's assessment, not to skip its updates. Systems without PHP, or without exposure to untrusted HTTP requests, are outside the scope described in its bulletin. [4]
For a business owner using WordPress, Drupal, Laravel or a custom PHP application, the useful question is simple: has the hosting environment been patched? A login screen is not evidence that the underlying runtime is protected.
The fixed upstream releases
| Branch | Fixed release |
|---|---|
| 8.5 | 8.5.12 |
| 8.4 | 8.4.27 |
| 8.3 | 8.3.36 |
| 8.2 | 8.2.35 |
These are the upstream emergency releases, not a universal version-number test. Distribution vendors may backport security fixes into packages carrying older version numbers. Obtain confirmation against both CVEs from your provider or distribution. [1] [4]
What to do now
- Identify the responsible person. Contact your host, server administrator or maintenance provider.
- Request explicit confirmation. Name both CVEs and ask whether every website and PHP worker uses a fixed package.
- Complete the deployment. Red Hat instructs administrators to restart every worker after configuration changes; containers need replacement. An updated file on disk does not necessarily mean the running service has changed. [4]
- Check essential functions. Verify forms, logins, checkout and uploads after maintenance.
- Keep the confirmation. Record the package, vendor advisory and completion date for your maintenance records.
If an exposed service cannot be patched promptly, have the administrator assess temporary restrictions or suspension while arranging the update. That is an operational decision based on the actual environment.
The October 23 follow-up
PHP also identified CVE-2026-115560, an unusual session upload-progress issue. It requires a particular session serializer configuration followed by a runtime change in application code. PHP recommends session.upload_progress.enabled=0 pending its next regular bugfix release; applications that never change the serializer at runtime are not exposed to that particular vector. [1]
Have the administrator apply any setting at the appropriate server configuration level and restart the workers. Disabling upload progress does not replace the emergency fixes for the original pair of vulnerabilities. [3] [4]
The rabbit's take
Your homepage may still load. Your dashboard may still report a happy collection of updated plugins. Neither answers the question that matters here. Get confirmation from the person responsible for PHP itself, and keep the answer on record.
Sources & reporting notes
- PHP project: October 20–23 announcements and advisories.
- PHP security advisory: RCE via OOM corruption.
- PHP security advisory: RCE via stale global state.
- Red Hat: PHP2Shell impact and deployment guidance.
Checked October 25, 2026. This report focuses on confirmed vendor guidance. Details may change; consult the linked advisories for current updates.