On November 19, 2026, A series of recently disclosed vulnerabilities in PHP has put one of the world’s most widely deployed web technologies under renewed scrutiny.
The most significant issues, CVE-2026-109618 and CVE-2026-109619, are critical remote code execution vulnerabilities that can allow an unauthenticated attacker to execute code on vulnerable PHP systems. CVE-2026-109618 carries a CVSS 4.0 score of 9.2 and has since been added to the CISA Known Exploited Vulnerabilities catalog.
A third issue, CVE-2026-115560, was disclosed shortly afterward. It involves a more specific PHP configuration and should be considered separately from the two original PHP2Shell vulnerabilities. Public reporting indicates PHP recommended temporarily disabling session upload progress for the affected configuration while awaiting the regular fix.
It lands just four weeks after PHP2Shell (CVE-2026-109618 and CVE-2026-109619), which attackers began exploiting within hours of disclosure. No exploitation of the new flaws has been reported so far. Given how fast PHP2Shell went from patch to attack, we don’t expect that window to stay open for long.
Check Point customers remain protected
Check Point has released IPS protections against attempts to exploit these PHP remote code execution vulnerabilities. Customers should ensure that their Security Gateways are running the latest IPS update and that the relevant protections are enabled in Prevent mode.
Check Point;s PHP Remote Code Execution advisories : CPAI-2026-15172 CPAI-2026-15184 covers CVE-2026-109618, CVE-2026-109619 and CVE-2026-115560 and is rated Critical
Importantly, IPS protection provides an additional layer of defense, but it does not replace updating PHP itself. Organizations should patch vulnerable installations as quickly as possible.
Here is what we know by now, who is exposed, and what to do about it.
What do we know by now
All seven critical flaws carry a CVSS 4.0 score of 9.2, and every one of them depends on specific configuration or runtime conditions. Several can lead to remote code execution (RCE).
Furthermore:
- This is PHP2Shell’s unfinished business. CVE-2026-115560 was left open by the October patches, and CVE-2026-129182 and CVE-2026-129481 extend the fixes for CVE-2026-109619.
- Session upload progress is now off by default. This is the feature PHP2Shell abused. Servers that set it explicitly keep it on.
- A local path to root. CVE-2026-129291 (high) lets an attacker who can run code in a PHP-FPM worker execute commands with the FPM master’s privileges, which is often root.
The release also fixes bugs in PHP-CGI, PHAR signature checks, SOAP and the HTTP stream wrapper. Full technical advisories are published on the PHP project’s GitHub.
Who’s exposed
Any server running PHP 8.2 through 8.5 below the fixed versions is affected. Whether a given flaw is reachable depends on how PHP is deployed. The setups at highest risk:
- PHP-FPM behind connection-reusing front ends. Nginx with fastcgi_keep_conn on, or Apache mod_proxy_fcgi with enablereuse=on (CVE-2026-129289). Reuse is off by default in both, so check custom configs and includes.
- Apps that keep session upload progress on and mix serializers (CVE-2026-115560), for example code that switches session.serialize_handler at runtime.
- PHP 8.5 deployments not using the production php.ini template, where zend.exception_ignore_args is left at 0 (CVE-2026-129474).
- Shared hosting and multi-tenant FPM pools, where one tenant’s code could escalate to the FPM master’s privileges (CVE-2026-129291).
- php-cgi with particular web server path mappings (CVE-2026-129538).
Two groups are easy to miss:
- End-of-life PHP. PHP 8.1, 8.0 and 7.4 get no official release. The PHP security team published minimal source backports, and some vendors are shipping their own. PHP 8.2 itself reaches end of life on December 31, 2026.
- PHP you didn’t install. Vendor products, appliances, admin portals and container base images often bundle their own PHP runtime. PHP2Shell showed that attackers go after exactly these edge-facing systems.
Organizations should look for PHP across:
- Internet-facing websites and web applications
- WordPress, Drupal, Joomla, Magento and other PHP-based environments
- PHP-FPM and Apache/mod_php deployments
- Shared hosting infrastructure
- Containers and cloud workloads
- Hosting and administration platforms
- Commercial applications and appliances that bundle PHP
- Legacy systems running unsupported versions of PHP
What needs to be done
- Upgrade PHP to 8.5.13, 8.4.28, 8.3.37 or 8.2.36. Linux distributions often backport fixes without changing the version number, so check the package changelog for the CVE IDs instead of relying on php -v.
- If you can’t patch today, apply the interim mitigations: Disable session upload progress: set session.upload_progress.enabled=0 in php.ini or the FPM pool config. It can’t be changed with ini_set(). Restart all workers and verify the value through the web server, not the CLI. Uploads still work; only server-side progress bars stop. Turn off FastCGI connection reuse (fastcgi_keep_conn in Nginx, enablereuse in Apache). Disable catch_workers_output in PHP-FPM pools. On PHP 8.5, set zend.exception_ignore_args=1.
- Disable session upload progress: set session.upload_progress.enabled=0 in php.ini or the FPM pool config. It can’t be changed with ini_set(). Restart all workers and verify the value through the web server, not the CLI. Uploads still work; only server-side progress bars stop.
- Turn off FastCGI connection reuse (fastcgi_keep_conn in Nginx, enablereuse in Apache).
- Disable catch_workers_output in PHP-FPM pools.
- On PHP 8.5, set zend.exception_ignore_args=1.
- For end-of-life PHP, apply your vendor’s backported fixes or the PHP security team’s source backports, and schedule the migration.
What should organizations do
- Find every PHP instance
Inventory PHP across the environment.
Start with internet-facing systems, but include containers, cloud workloads, third-party products, appliances and applications that may bundle PHP internally.
Organizations using external hosting providers should also confirm which PHP version the provider is actually running.
- Patch PHP, not just the application
Move supported PHP branches to their appropriate fixed releases.
Do not assume that updating WordPress, Drupal, Magento or another CMS resolves the issue. The underlying PHP runtime must be addressed.
After updating, restart PHP-FPM, Apache or the relevant web service and verify that the patched PHP version is actually running.
- Treat unsupported PHP as a priority
Older versions create a different remediation challenge.
PHP’s current lifecycle information shows that PHP 8.1 and earlier are end-of-life. See PHP’s official branch status. [php.net]
For those systems, administrators should check whether their Linux distribution or commercial vendor provides a maintained backport. Where that isn’t possible, migration or isolation should be prioritized.
- Reduce exposure where immediate patching isn’t possible
Where vulnerable systems cannot immediately be updated:
- Restrict internet access.
- Apply access controls where possible.
- Segment affected web servers from sensitive internal systems.
- Limit unnecessary outbound connectivity.
- Consider temporarily taking particularly exposed systems offline.
These measures reduce risk, but they are not substitutes for applying the appropriate PHP security update.
- Make sure preventive protections are enabled
Check Point customers should update IPS and verify that the PHP Remote Code Execution protections are active.
The Check Point advisory provides the applicable protection and configuration guidance for Security Gateway customers. Check Point PHP Remote Code Execution protection. [advisories…kpoint.com]
This follows CPR’s earlier operational guidance to keep critical IPS protections updated and use Prevent mode after appropriate validation. [COMMS week…y catch up | Teams]
- Don’t stop at patching. Look backward.
Patching closes the vulnerability, but it does not determine whether the system was compromised before it was patched.
That consideration is particularly important now that CVE-2026-109618 appears in CISA’s Known Exploited Vulnerabilities catalog. . [nvd.nist.gov]
Security teams should therefore investigate vulnerable or previously vulnerable systems for indicators such as:
- Web server or PHP processes unexpectedly spawning shells
- New or unfamiliar PHP files appearing in web roots
- Unexpected outbound connections from web servers
- Unusual HTTP requests to PHP endpoints
- PHP worker crashes or unexplained service restarts
These behaviors are consistent with the hunting guidance developed in CPR’s PHP2Shell_Threat_Report_CVE-2026-109618_109619. [PHP2Shell_…618_109619 | PDF]
How Check Point protects customers
Check Point has released IPS protections covering both CVE-2026-109618 CVE-2026-109619 Customers with IPS enabled on Check Point Security Gateways are protected.
Stay up to date with the Vulnerability Response Point
When critical vulnerabilities hit, head to the Check Point Vulnerability Response Point for live research as events unfold. It helps you understand:
- What’s at risk
- What to patch
- How to stay protected
Check Point Research continues to monitor for exploitation and will update this post as more becomes known.











