- SMB/SME
- Enterprise
· ASC Editorial Team
After PHP2Shell, Another Critical PHP Patch: What It Means for Your Web Servers and Firewalls
On 19 November 2026, PHP released security updates for all its supported versions: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. Seven of the flaws fixed are rated critical, and several can lead to code being run on a server without logging in. PHP says the most serious "require either non-default configuration or uncommon setups". No attacks using the new flaws had been reported by 20 November.
The release follows PHP2Shell, the two PHP flaws that attackers used last month against Palo Alto firewalls and Check Point gateways. One of the new fixes dates from that time. On 23 October, PHP disclosed CVE-2026-115560, a flaw in session upload progress, a feature that tracks file uploads, and advised turning the feature off until a fix was ready. That fix has now arrived. Upload progress is now off by default, but a server where it has been switched on explicitly keeps it on.
The critical flaws depend on particular settings: - CVE-2026-115560 needs upload progress turned on, and applications that read the same session data in different formats. - CVE-2026-129289, in PHP-FPM, the component that runs PHP behind most web servers, can let an attacker run code without logging in. It needs the web server to reuse its connections to PHP-FPM, and an application that leaves part of a request unread. - The others need particular error-handling settings, or affect PHP 8.5 only.
Uncommon doesn't mean absent, and you won't know without checking your configuration.
A further flaw, CVE-2026-129291, rated high, matters after an attack. Someone who can already run code in a PHP-FPM worker can run commands with the main PHP-FPM process's privileges, which are often root. That can turn a foothold in a website into control of the whole server.
Version numbers can mislead. Linux distributions often backport fixes without changing the version, so check your package's changelog for the CVE numbers rather than relying on the version PHP reports. Updating WordPress, Drupal or another application doesn't update PHP itself, and PHP-FPM or the web server must restart before the fix takes effect. PHP 8.2 reaches end of life on 31 December 2026, and older versions get no official releases at all.
The firewall vendors have responded differently: - Check Point says its IPS protections CPAI-2026-15172 and CPAI-2026-15184 cover the PHP2Shell flaws and CVE-2026-115560. For CVE-2026-129289, it says its gateways drop the malformed traffic when its "Non Compliant HTTP" setting is turned on, with HTTPS Inspection for encrypted traffic. It doesn't say whether any Check Point products are affected by the new flaws. - Palo Alto Networks says its analysis shows no impact of CVE-2026-115560 on PAN-OS firewalls or Panorama, because the flaw needs a configuration PAN-OS doesn't use. It had published nothing on the other new flaws by 20 November. - Fortinet updated its PHP2Shell outbreak report on 19 November to include the new release. It doesn't say whether its products are affected by the new flaws, or which of its protections cover them.
Three steps follow.
First, find every PHP: on your own servers, in container images, in products and appliances you bought, and with hosting providers. Ask the vendors and providers which versions they run and when they'll update.
Second, update, internet-facing servers first, and restart PHP-FPM or the web server. If you can't update straight away, set session.upload_progress.enabled=0 in the PHP or PHP-FPM configuration, not in application code, and turn off FastCGI connection reuse in the web server. Check the result through the web server: PHP's command line uses its own configuration and can show a different answer.
Third, if you rely on a firewall's intrusion prevention while you patch, check that the relevant protections are updated, turned on and set to block, not only to detect. Where your vendor hasn't said what covers these flaws, ask. And if any server ran with upload progress on through the PHP2Shell attacks, Check Point advises checking it for signs of compromise, not only patching it.
Could you say today which of your PHP servers have session upload progress switched on?
Source: Check Point: New PHP Vulnerabilities: What Organizations Need to Know
Get Insights by email
A short round-up of new articles every Monday morning. Nothing else.