Skip to main content
PHP

PHP flaws fixed in October used to take over firewalls, security firms say

PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix two critical flaws that can let attackers run code on a web server without logging in. CISA lists both as exploited. What to check with your host.

By Published Updated
Illustration: a cartoon robot raising a warning shield beside a server rack with a command-line window bursting out of it

Updated, 19 November 2026, 14:17 GMT. PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 this afternoon, with seven fixes rated critical. They include the CVE-2026-115560 fix described below, and PHP’s advisories say two of the new fixes cover cases its October fix for CVE-2026-109619 didn’t reach. A server patched for PHP2Shell in October needs this update too. Our article on today’s release has the details and a note to send your host.

Updated, 19 November 2026, 07:32 GMT. If someone looks after your server, ask them now to plan a PHP update for this afternoon. PHP says it will release security fixes for every supported version today, Thursday 19 November, between 14:00 and 14:30 GMT. It rates the most serious of them critical, but says those “require either non-default configuration or uncommon setups”. It will publish the details and version numbers with the releases.

This is PHP’s next regular release. On 23 October PHP said that release would come with a full advisory on CVE-2026-115560, covered below. Its notice for today doesn’t name that flaw. We’ll add the details when PHP publishes them.

Updated, 16 November 2026, 12:37 GMT, with Dream’s and Palo Alto Networks’ reports of attackers using PHP2Shell to take over Palo Alto firewalls, and a check for businesses with a Palo Alto or Check Point firewall. Earlier updates added Check Point’s report, a timeline, a note to send your host and PHP’s follow-up advice from 23 October. This article has also been corrected. See Changes at the end.

Two critical PHP flaws fixed on 21 October can let an attacker run code on a web server without logging in, and the US Cybersecurity and Infrastructure Security Agency (CISA) lists both as exploited in real attacks. The fix is a PHP update on the server.

That puts the fix with your host or whoever runs your server. PHP runs underneath WordPress and many of the other tools small business sites are built on.

What happened

On 20 October the PHP project gave notice of a security release for two vulnerabilities, both rated 9.2 out of 10 on CVSS v4.0. On 21 October it released PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, fixing CVE-2026-109618 and CVE-2026-109619, which became known as PHP2Shell.

PHP says the flaws “can allow unauthenticated remote code execution” and affect every PHP installation serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. It considers the risk highest for Apache with mod_php. Its release notes say “there are no complete mitigations, updating is the only safe choice.”

Amazon’s threat intelligence team recorded an exploitation attempt against one of its honeypots on 17 October, four days before the fix was published. On 26 October CISA added both flaws to its Known Exploited Vulnerabilities catalogue, its list of flaws with evidence of being used in real attacks.

On 26 October the Israeli security company Dream reported that attackers had chained PHP2Shell with a Linux kernel flaw to take full control of 25 servers in the US, Japan, Taiwan and South Korea.

Twenty-four were Palo Alto Networks firewalls running PAN-OS 12.1 or 12.2, and the 25th was a firewall management server reached from one of them. Three were in a US government-affiliated network.

Dream says the first of the government-affiliated firewalls was taken over on 23 October. It doesn’t name the attackers, and Unit 42 says the activity comes from a Chinese-speaking attacker it tracks as CL-UNK-1280.

Palo Alto Networks’ advisory, updated on 29 October, says active exploitation has been seen against firewall management interfaces exposed to the internet, and its Unit 42 team says it independently verified Dream’s results. The advisory lists fixed PAN-OS versions for each affected branch, and Unit 42 tells customers to remove public internet access to the management interface.

On 12 November the security company Check Point reported that attackers had used PHP2Shell to target unpatched Check Point Security Gateways, its own network security products, through their Mobile Access portals, and had got into some of them. It describes a first wave on 30 October against Israeli organisations, including destructive activity against some of them, and a broader second wave on 2 November across several countries and sectors, with no evidence of destructive activity. Check Point says the attempts looked opportunistic rather than aimed at particular sectors.

The Check Point gateways’ login portals run on Apache and PHP. None of Dream, Palo Alto Networks or Check Point says ordinary web servers or websites were attacked.

The UK’s National Cyber Security Centre says organisations using any version of PHP are affected and should update, starting with internet-facing systems. Where that isn’t possible, they should apply PHP’s temporary mitigations, and if they can’t do that either, or it would take too long, consider taking the system offline until it is fixed.

Why WordPress sites were caught up in it

The flaws are in PHP itself, and WordPress.org said on 21 October that no WordPress update is required or planned. Almost every WordPress site runs on PHP, so the fix is on the hosting side. WordPress.org’s advice was to check with your host and get PHP updated.

PHP 8.1 and older no longer get updates from the PHP project. PHP published minimal source patches for 7.4, 8.0 and 8.1 for people who build PHP themselves, and some Linux distributions and long-term support vendors offer their own backported fixes.

PHP 8.2 itself reaches end of life on 31 December 2026, so a site on 8.2 that has been patched for PHP2Shell still needs to move to a newer version within weeks.

What to check now

Linux distributions often patch PHP without changing the version number, so the number your site shows can’t tell you whether the server was updated. Ask your host.

In WordPress you can see your PHP version under Tools, then Site Health, then Info, then Server. If it says anything older than 8.2, the PHP project no longer supports it.

If your business has a Palo Alto Networks firewall or Panorama, or a Check Point Security Gateway, ask whoever looks after it whether the vendor’s fixes for these attacks are installed, and whether the Palo Alto management interface or the Check Point Mobile Access portal can be reached from the internet.

A follow-up from PHP on 23 October

Two days after the release, PHP published an informational advisory about what it called “an unlikely RCE vector”, now numbered CVE-2026-115560. PHP says it can only happen with an unusual mix of settings and application code, and it held the fix for its next regular bugfix release, which came on 19 November.

Until then, PHP suggested keeping session.upload_progress.enabled=0 set in the server’s php.ini or PHP-FPM pool, not through .user.ini, and restarting PHP. That setting was already one of PHP’s 21 October mitigations. The 19 November releases switch upload progress off by default, but a server that has it switched on explicitly in its configuration keeps it on after the update, PHP says.

Still unknown

How widely PHP2Shell has been exploited against ordinary websites and hosting. The published attacks we’ve found are Amazon’s honeypot sighting, where Amazon hasn’t said whether the attempt succeeded, and the attacks on firewalls and security gateways reported by Dream, Palo Alto Networks and Check Point. Whether any of the flaws fixed on 19 November has been used in attacks is also unknown.

Changes

Update, 19 November 2026, 14:17 GMT: Added PHP’s 19 November releases, which fix CVE-2026-115560 and two cases the October fix didn’t cover, with a link to our article on them, and updated the timeline and what is still unknown.

Update, 19 November 2026, 07:32 GMT: Added PHP’s 18 November notice of critical security releases due today between 14:00 and 14:30 GMT, with the dates in the timeline.

Correction, 16 November 2026, 12:37 GMT: The 07:37 GMT update said Check Point’s 12 November report was the first published report we’d found of PHP2Shell being used to break into real systems. Dream reported such attacks on 26 October, and Palo Alto Networks had said by 29 October that it had seen active exploitation. We had listed Dream’s research as not yet checked.

Update, 16 November 2026, 12:37 GMT: Added Dream’s and Palo Alto Networks’ reports of PHP2Shell being used to take over Palo Alto firewalls, with their dates in the timeline, a check for businesses with a Palo Alto or Check Point firewall, and updated what is still unknown.

Update, 16 November 2026, 07:37 GMT: Added Check Point’s 12 November report of PHP2Shell being used to break into some Check Point Security Gateways, with the dates in the timeline, and updated what is still unknown.

Update, 13 November 2026, 14:19 GMT: Added a timeline and a note to send your host, and moved the NCSC’s advice on checking for compromise into that note.

Update, 13 November 2026, 11:33 GMT: Added PHP’s 23 October advisory on CVE-2026-115560 and the NCSC’s advice to check unpatched servers for compromise. Linked the PHP, NCSC and Amazon sources directly rather than through a news report.

Correction, 13 November 2026, 11:33 GMT: The first version:

  • said the NCSC told organisations to consider taking systems offline if they couldn’t be fixed straight away. The NCSC’s advice is to update, or apply PHP’s temporary mitigations if you can’t, and to consider taking a system offline only if you can do neither.
  • told readers to check their PHP version against the fixed releases. Linux distributions often patch PHP without changing the version number, so the article now says to ask your host whatever the number shows.

What to ask your host

Copy this to your host or whoever runs your server:

Has the server my website runs on been updated to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36, released on 19 November, or to patched packages from your Linux distribution? Those fix CVE-2026-115560 and cases the October PHP2Shell fix didn’t cover. If it wasn’t updated for PHP2Shell (CVE-2026-109618 and CVE-2026-109619) straight away in October, have you checked it for signs of compromise, such as backdoors, as the NCSC advises? Is session upload progress switched off? And if my site is on PHP 8.2 or older, when can it move to a newer version?

Our free PHP vulnerability check lists the fixed releases if you’d rather start there, though only your host can confirm the server is patched.

Timeline

  • 17 October: Amazon records an exploitation attempt against one of its honeypots.
  • 20 October: PHP gives notice of a security release for two critical flaws.
  • 21 October: PHP releases 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Amazon publishes its 17 October sighting.
  • 23 October: PHP advises turning off session upload progress to close “an unlikely RCE vector”, CVE-2026-115560, until its next bugfix release.
  • 23 October: Attackers take over a Palo Alto firewall at a US government-affiliated organisation, Dream later reports.
  • 26 October: Dream publishes its findings.
  • 26 October: CISA adds both flaws to its catalogue of exploited vulnerabilities.
  • 29 October: Palo Alto Networks’ Unit 42 says it has verified Dream’s results, and that PHP2Shell is being exploited against PAN-OS management interfaces exposed to the internet.
  • 30 October: Attackers use PHP2Shell against Check Point Security Gateways at Israeli organisations, Check Point later reports.
  • 2 November: A second, broader wave targets organisations with Check Point gateways in several countries, with no evidence of destructive activity, Check Point later reports.
  • 12 November: Check Point publishes its findings.
  • 18 November: PHP gives notice of security releases for all supported versions, the most serious rated critical.
  • 19 November: PHP releases 8.5.13, 8.4.28, 8.3.37 and 8.2.36, fixing CVE-2026-115560 and two cases the October fix for CVE-2026-109619 didn’t cover, PHP says.
  • 31 December 2026: PHP 8.2 reaches end of life.

Alex De Sousa is the founder of Digital Royalty, a software development company in Portsmouth that builds websites, web apps and AI tools for UK businesses.