PHP2Shell Explained: What to Do Now (Live Updates)

On this page
PHP2Shell is the name for two critical flaws in PHP, the language behind most websites, that let attackers run their own code on a web server without logging in.[1][2] Fixes came out on October 21, 2026, and attacks have already started.[1][3] If your site runs on PHP, make sure the server is updated today.
Status (Nov 10, 2026): active. Last checked Nov 10, 2026: no major changes since Nov 7. Fixed PHP versions are out and attacks are under way.[1][3] Wordfence still knows of no WordPress site broken into through PHP2Shell, but says that doesn’t make an unpatched server safe.[10] Attackers have taken over Palo Alto firewalls with exposed management interfaces, and Palo Alto has released all of its fixed builds.[12][14] CISA lists both PHP flaws and the Linux kernel flaw used in that chain as known exploited vulnerabilities.[11] Cisco has fixed Expressway and Duo; two Cisco wireless products still await a fix.[15] Singapore’s cyber agency also lists Citrix, F5, Siemens and Fortinet FortiSOAR as affected.[17] Fortinet says the flaws can only crash FortiSOAR, and it has fixes out.[18] PHP’s extra setting still applies (see below).[1] Separately, Cloudflare has seen forged eMudhra certificates made with the leaked keys (see below).[16]
TL;DR: What to do right now
- On managed hosting? Ask your host whether your server runs a patched PHP build, and get it in writing. Many hosts patched within a day.[7]
- Run your own server? Update to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 (or your Linux vendor’s patched package), then restart every PHP process.[1][2] Install Linux kernel updates too: attackers have paired PHP2Shell with a kernel flaw to get root.[11]
- Can’t update today? Apply PHP’s temporary settings below, or take the site offline until it’s fixed, as the UK NCSC and the FBI advise.[5][6]
- On PHP 8.1 or older? There’s no official update. Upgrade, use a vendor backport, or take it offline.[1][7]
- Already updated? Also set
session.upload_progress.enabled=0until PHP’s next regular release, as PHP advised on October 23.[1] - Check for signs of a break-in going back to October 17, not just to the release date.[3]
Latest updates
- Nov 7, 2026: Fortinet’s PSIRT advisory FG-IR-26-186 (updated November 5) confirms that FortiSOAR and FortiSOAR PaaS run affected PHP versions. It says the impact on them is limited to a denial-of-service condition, not code execution, and lists them as not known to be exploited.[18] FortiSOAR 8.0.1 is fixed, patches are out for 8.0.0, 7.6.7 and 7.5.4, 7.6.8 and 7.5.5 are coming, and older branches must move to a fixed release. FortiDDoS is still under investigation.[18] PHP, CISA, Palo Alto and Cisco have posted nothing new on PHP2Shell since November 6.[1][11][14][15]
- Nov 6, 2026: Singapore’s CSA updated its alert again on November 6. Its list of affected products now also includes Fortinet FortiSOAR and FortiSOAR PaaS running affected versions.[17] Fortinet’s own advisory is covered in the Nov 7 entry.
- Nov 5, 2026: Singapore’s Cyber Security Agency (CSA) issued an alert on November 3, updated November 5, on active PHP2Shell exploitation of network and security products.[17] Besides Palo Alto and Cisco, its list of affected products includes Citrix NetScaler ADC and Gateway, F5 BIG-IP APM and its Configuration utility, and Siemens RUGGEDCOM APE1808 devices running affected PAN-OS versions. CSA says the list is not exhaustive.[17] It advises applying vendor updates immediately and limiting management interfaces to trusted networks.[17]
- Nov 3, 2026: In the separate eMudhra certificate incident, Cloudflare reported forged certificates made with the leaked keys, but no evidence so far that they were used to intercept its connections.[16] We updated the eMudhra section below.
- Nov 2, 2026: Cisco marked its PHP2Shell advisory final on October 30. Fixed releases are out for Expressway and Expressway Select (15.5.21) and Duo Access Gateway (3.2.0). Cisco fixed ISE Portal Builder itself.[15] Ultra-Reliable Wireless Backhaul and Unified Industrial Wireless Software are still affected, with a fixed release, 26.2.1.9, expected in November 2026.[15] PHP, Palo Alto and CISA have posted nothing new on PHP2Shell since our last update.[1][11][14]
- Nov 1, 2026: Wordfence said on October 28 that it knows of no WordPress site compromised through PHP2Shell.[10] Its monitoring rule logged about 77,600 related requests from more than 2,000 IP addresses between October 23 and 27, all attacks or automated scanning.[10]
- Oct 31, 2026: Dream updated its report on October 29 and now names Palo Alto Networks PAN-OS firewalls as the devices taken over in the chained campaign.[12] Palo Alto’s advisory, also updated October 29, lists the last pending build, 11.1.7-h12, as released, so every fixed PAN-OS build is now out.[14]
- Oct 30, 2026: Unit 42 says it independently verified the tooling behind the chained campaign Dream reported and confirmed its results. It says about 0.02% of Palo Alto’s installed base had internet-facing management interfaces and was impacted.[13] CISA added the Linux kernel flaw in that chain (CVE-2026-46300) to its KEV catalog on October 28.[11]
- Oct 29, 2026: Security firm Dream reported an attacker who chained PHP2Shell with a Linux kernel flaw (CVE-2026-46300) to take over 25 servers in four countries, starting with firewalls whose management interface was open to the internet.[12]
- Oct 28, 2026: Palo Alto now says it has seen active exploitation targeting PAN-OS management interfaces exposed to the internet. It raised the issue to critical, with its highest urgency rating.[14] Keep the management interface limited to trusted internal addresses and install the hotfix.[14] Correction: on October 25, Unit 42 retracted its October 23 report. It can’t confirm that an attack on a European government agency came in through PHP2Shell.[13] We have removed that claim from this article.
- Oct 27, 2026: CISA added both PHP2Shell flaws to its Known Exploited Vulnerabilities (KEV) catalog on October 26, with an October 29 deadline for US federal civilian agencies.[11]
- Oct 25, 2026: Palo Alto released its first fixed PAN-OS builds.[14] An earlier version of this note described a Unit 42 report of a government break-in, which Unit 42 has since retracted (see Oct 28).[13]
- Oct 23, 2026: PHP published an advisory for a separate, related flaw, CVE-2026-115560, and suggests everyone set
session.upload_progress.enabled=0until the next regular bugfix release.[1] - Oct 22, 2026: Palo Alto said all PAN-OS and Panorama versions were affected. Fortinet began checking 12 products and Cisco 31.[5] The FBI and NSA urged organizations to patch or take systems offline.[6] Most large WordPress hosts reported they had patched or blocked attacks.[7]
- Oct 21, 2026: PHP released fixes at 14:00 UTC.[1] Amazon says PHP2Shell is now being broadly exploited.[3] Patchstack reported multiple confirmed exploitation incidents.[7] CISA and the UK NCSC issued alerts.[5][8]
- Oct 20, 2026: Details leaked online, and PHP announced an emergency release for the next day.[1][8]
What PHP2Shell is, in plain English
PHP is the software that builds pages on a huge share of websites. W3Techs says PHP runs 69.3% of sites whose server language it can identify.[6] WordPress, Drupal, Joomla, Magento and WooCommerce all run on it.
Think of a PHP server as a busy restaurant kitchen. Each web request is an order. PHP2Shell is a set of mistakes in how the kitchen cleans up between orders. If an attacker sends a carefully built order, the cleanup goes wrong, and leftovers from one order get used in the next. With the right timing, that lets the attacker slip in their own instructions and run them on the server.[2]
Running code on the server is the worst outcome. The NSA warns the flaws can give attackers a direct path to the server’s files or database.[6] From there they can steal data, plant malware or use the server to attack others. Your WordPress login, plugins and passwords don’t stop this, because the attack happens inside PHP itself.[2]
The technical version
- CVE-2026-109618 (out-of-memory corruption): When memory runs out mid-request, PHP can abandon a request with data only partly set up. Cleanup then treats that data as valid. Crafted multipart requests can trigger it even within configured size limits.[2]
- CVE-2026-109619 (stale global state): A use-after-free. Internal state can keep pointing at memory freed after an earlier request, and a later request on the same worker can use it. Session upload progress, on by default, is one confirmed path.[2]
- Both are rated CVSS v4.0 9.2 (critical) and need no login.[1][2]
How and when it was found
Researchers from Wiz, OpenAI and Calif found the flaws in August. Calif and OpenAI independently reported the out-of-memory issue on August 11.[4] Wiz used several AI models in its research, and Calif used an OpenAI model to find one flaw.[6]
| Date (2026) | What happened |
|---|---|
| August | Flaws found and privately reported to PHP.[4] |
| Oct 17 | Amazon’s honeypots logged an exploit attempt, four days before disclosure. How the attacker knew is unclear.[3] |
| Oct 20 | CVE details leaked online. PHP scheduled an emergency release for 14:00 UTC the next day.[1][8] |
| Oct 21 | PHP released fixes. Exploit code appeared within hours and was used against sensors almost at once.[1][3] |
| Oct 22 | FBI and NSA advice. Appliance vendors began reporting affected products.[5][6] |
| Oct 23 | PHP advisory for a related flaw, CVE-2026-115560, with one setting to change.[1] |
| Oct 23–24 | Per Dream, an attacker takes over 25 servers through exposed firewall management interfaces, three at a US government-affiliated organization.[12] |
| Oct 23–25 | Palo Alto ships its first fixed PAN-OS builds. Unit 42 retracts an earlier report of a government break-in tied to PHP2Shell.[13][14] |
| Oct 26 | CISA adds both flaws to its KEV catalog, with an October 29 deadline for federal agencies.[11] |
| Oct 27–29 | Palo Alto reports attacks on exposed PAN-OS management interfaces, raises the issue to critical and ships all of its fixed builds.[14] |
| Oct 28–29 | CISA lists the Linux kernel flaw used in the chain. Dream names Palo Alto as the firewall vendor, and Unit 42 verifies the campaign and says about 0.02% of Palo Alto’s installed base was impacted.[11][12][13] |
Who is affected
Every PHP installation that serves web requests is at risk until it is updated.[1] Some setups are riskier than others:
| Setup | Risk | Notes |
|---|---|---|
| Apache with mod_php | Highest | A demonstrated exploit runs before any site code loads.[1] |
| PHP-FPM (common on Nginx hosts) | High | One attack path is blocked, but another was confirmed.[2] |
| php-cgi, FrankenPHP, LiteSpeed | At risk | Named by PHP as affected.[1] |
| PHP 8.1, 8.0, 7.x and older | Highest, long term | No official updates. Only source backports for 7.4, 8.0 and 8.1.[1] |
| Appliances and products that bundle PHP | Varies | Palo Alto PAN-OS and Panorama are affected through the management web interface, and Palo Alto reports attacks on exposed ones. All fixed builds are now out.[14] Dream reports a campaign that took over Palo Alto firewalls through exposed management interfaces.[12] Unit 42 says it verified that campaign’s tooling, and about 0.02% of Palo Alto’s installed base was impacted.[13] Cisco has fixed releases out for Expressway (15.5.21) and Duo Access Gateway (3.2.0); two Cisco wireless products are due a fix in November 2026.[15] Singapore’s CSA also lists Citrix NetScaler ADC and Gateway, F5 BIG-IP and Siemens RUGGEDCOM APE1808 as affected; check those vendors’ advisories.[17] It also lists Fortinet FortiSOAR and FortiSOAR PaaS.[17] Fortinet says the impact there is limited to denial of service; FortiSOAR 8.0.1 and patches for 8.0.0, 7.6.7 and 7.5.4 fix it, and FortiDDoS is still under investigation.[18] |
The long tail is large. VulnCheck counted about 2.6 million internet-facing hosts running PHP. Over 700,000 of them run PHP 3.x through 7.3, which will never get a fix.[8]
Who doesn’t need to worry (or has less to do)
- Website visitors. This is a server flaw. Nothing on your phone or laptop needs an update for PHP2Shell.[2]
- WordPress.com, WordPress VIP, WP Cloud and Pressable customers. Automattic says they were protected before the release, with nothing to do.[7]
- Sites that don’t run PHP at all, such as purely static sites. The flaws are in PHP itself.[1]
- WordPress itself. The WordPress Security Team says no WordPress update is needed or planned. Updating plugins or themes won’t fix PHP2Shell either.[7]
Being behind Cloudflare lowers your risk but doesn’t remove it. Cloudflare deployed firewall rules for all plans, including free, and calls them a stopgap.[5][7]
How it’s being addressed
- PHP released 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Linux vendors got patches in advance.[1] PHP 8.2 reaches end of life on December 31, 2026, so 8.3 or newer is the better target.[1]
- Hosts such as SiteGround, WP Engine, Kinsta, Hostinger and 20i report patching or blocking. GoDaddy’s regular web hosting was still relying on mitigations on Oct 22, and Bluehost had patched most servers.[7]
- Firewalls: Cloudflare’s rules are live, and attackers are already changing payloads to slip past them.[5][8]
- Governments: CISA, the FBI and the UK NCSC urged immediate patching, or taking systems offline if that isn’t possible. The NSA told organizations to prepare for the update.[5][6][8] On October 26, CISA added both flaws to its Known Exploited Vulnerabilities catalog, with an October 29 deadline for federal agencies.[11] On October 28 it added the Linux kernel flaw used to gain root in Dream’s chained attacks.[11] On November 3, Singapore’s CSA warned of active exploitation against network and security products and told organizations to restrict management interfaces.[17]
“There are no complete mitigations, updating is the only safe choice.”
PHP release notes [1]
If you run your own server
First, confirm which PHP actually serves your pages. The command-line PHP can differ from the one your web server uses. Linux vendors ship their own patched packages, so check your vendor’s advisory, not just the version number.[2]
php -v # command-line PHP
php-fpm -v # FPM (may be php-fpm8.3)
apachectl -M | grep -i php # is mod_php loaded?After updating, restart PHP-FPM or Apache so every worker runs the new code, and rebuild containers.[2][7] If you can’t update right away, PHP lists partial mitigations. They reduce specific attack paths but don’t make a server safe.[1] The first line below is now recommended for every server, patched or not, until PHP’s next regular release.[1]
; php.ini or FPM pool, then restart all workers
session.upload_progress.enabled = 0
fatal_error_backtraces = 0 ; PHP 8.5 only
post_max_size = 8M ; 32M if you need uploads
memory_limit = -1 ; prefer php_admin_valueSettings changed with ini_set() or .user.ini apply too late to help.[1] Setting memory_limit = -1 removes PHP’s per-request memory cap, so restore a normal limit once you’ve patched.
How to check for a break-in
These attacks can leave almost no trace. CrowdStrike says requests return a normal response, and the only server-side sign may be an often-ignored memory-limit error.[8] Look back to October 17:[3]
- POST requests containing
PHP_SESSION_UPLOAD_PROGRESSin your web logs.[3] - PHP processes that start command shells or download files, which the FBI flags.[6]
- Unfamiliar PHP files, new scheduled tasks, unknown admin accounts and odd outbound connections, per Sucuri.[7]
- On firewalls and appliances: a small PHP web shell in a public folder and a reverse SSH tunnel set to start at boot, the traces Dream found.[12]
Wordfence advises keeping logs from at least 48 hours before the release.[7] If you find signs of compromise, isolate the server and keep the logs. Our Rank Math PRO malware recovery order walks through cleanup steps that apply here too. In the US, you can report incidents to the FBI’s IC3.[6]
“an unpatched server should not be considered safe.”
Alex Thomas, Wordfence [7]
A separate incident: the eMudhra certificate keys
The same week brought a second, unrelated internet-trust problem. Certificate authorities (CAs) are the companies browsers trust to vouch that a website is real. The private keys for eight eMudhra intermediate CA certificates were generated with too little randomness, so anyone could compute them from the public certificates.[9] With those keys, an attacker could fake a trusted certificate for almost any site to software that still trusts them.[9]
- Browsers are covered. Chrome and Firefox blocked the certificates on October 17, Apple on October 19 and Microsoft on October 20.[9]
- Forged certificates exist. eMudhra says only one of the eight was in production and none issued customer certificates.[9] But Cloudflare has seen certificates forged with the leaked keys, the first within hours of the weakness going public. It has found no evidence so far that they were used to intercept its connections, and says that doesn’t rule out targeted attacks.[16]
- Many clients still trust the chain. On large networks, more than half of Cloudflare’s test connections still accepted it as of October 30. Up-to-date browsers are mostly patched; bots and old browsers are not.[16]
- PHP sites: update your operating system’s CA certificates and, if you use Composer, the
composer/ca-bundlepackage (1.6.0 or 1.4.16).[9] - If your site certificate chains to emSign ECC Root CA – G3, replace it now: Google scheduled its removal from Chrome for October 27.[9]
PHP2Shell is a reminder that your site depends on server software you may never see, like the Ghostscript flaw in WordPress PDF uploads we covered last week.
Where Zero Spam fits
Zero Spam doesn’t patch PHP and can’t block this attack. Only a PHP update fixes it. What it does is block spam bots and known bad IPs on your site, which cuts the junk traffic that hides real problems in your logs. The free Zero Spam WordPress plugin is a good habit once your server is patched, and you can start on the free Explorer plan.
FAQ
Frequently Asked Questions
PHP2Shell is the name for CVE-2026-109618 and CVE-2026-109619, two critical PHP flaws that let attackers run code on a web server without logging in. PHP fixed them on October 21, 2026.[1][2]
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, or a Linux vendor package with the fix. PHP 8.1 and older get no official update.[1]
If your server runs an unpatched PHP, yes. WordPress itself needs no update. Check Tools, Site Health, Info, Server, and ask your host whether its PHP is patched.[7] As of October 28, Wordfence knew of no WordPress site compromised through PHP2Shell.[10]
Yes. Amazon saw an attempt on October 17 and says it is now broadly exploited. CISA added both flaws to its known-exploited list on October 26, Palo Alto reports attacks on exposed PAN-OS firewalls, and Dream describes a campaign that took over 25 servers, mostly Palo Alto firewalls, which Unit 42 says it verified.[3][11][12][13][14]
Partly. Cloudflare added firewall rules on all plans, including free, but calls them a stopgap. You still need the PHP update.[5][7]
No. It is a separate incident involving weak certificate keys. Browsers already block the certificates. Update your operating system and CA bundles.[9]
Sources & References
- PHP: Security advisory for CVE-2026-109618 and CVE-2026-109619, fixed releases and partial mitigations (Oct 21, 2026); session upload progress advisory, CVE-2026-115560 (Oct 23, 2026); Windows Brotli builds (Oct 26, 2026)
- Rapid7: Technical analysis of both CVEs, affected setups, preconditions and mitigations (Oct 21, 2026)
- Amazon Threat Intelligence: PHP2Shell exploitation seen in MadPot honeypots before disclosure (Oct 21, 2026)
- SecurityWeek: PHP2Shell patches land as first exploitation attempts hit sensors, discovery by Wiz, OpenAI and Calif (Oct 21, 2026)
- Help Net Security: PHP2Shell patched, NCSC advice, Cloudflare WAF, Palo Alto, Fortinet and Cisco updates (updated Oct 22, 2026)
- Newsweek: FBI and NSA advice on the PHP flaws, W3Techs PHP usage (Oct 22, 2026)
- The Repository: WordPress hosts' patch status, WordPress Security Team, Patchstack, Wordfence and Sucuri on PHP2Shell (Oct 22, 2026)
- The Hacker News: PHP2Shell exploit attempt before disclosure, CISA alert, VulnCheck exposure counts (accessed Oct 22, 2026)
- The Hacker News: Eight eMudhra CA keys compromised, browser and software fixes (updated Oct 21, 2026)
- Wordfence: PHP2Shell update, no confirmed WordPress compromises; about 77,600 related requests from 2,000+ IPs, Oct 23–27 (Oct 28, 2026)
- CISA: Known Exploited Vulnerabilities catalog, both PHP2Shell flaws added Oct 26 with a federal due date of Oct 29, Linux kernel CVE-2026-46300 added Oct 28 and chainable with PHP2Shell (Oct 30, 2026)
- Dream Research: Chained PHP2Shell exploit roots 25 servers, including US government-affiliated systems; names Palo Alto Networks PAN-OS as the firewall vendor (updated Oct 29, 2026)
- Unit 42 (Palo Alto Networks): Threat brief; Oct 25 retraction of the Oct 23 report; Oct 29 update verifying the Dream-reported chained campaign, about 0.02% of installed base impacted (updated Oct 29, 2026)
- Palo Alto Networks: PHP2Shell impact on Palo Alto products, active exploitation of exposed PAN-OS management interfaces, all fixed builds released (updated Oct 29, 2026)
- Cisco: PHP vulnerabilities affecting Cisco products, fixes for Expressway 15.5.21 and Duo Access Gateway 3.2.0, ISE Portal Builder fixed by Cisco, wireless fix 26.2.1.9 due November 2026 (Oct 30, 2026)
- Cloudflare: Tracking exploitation and patching of eMudhra’s weak keys; forged certificates made after the keys leaked, no evidence of interception so far, more than half of probes on large networks still accept the chain (Oct 30, 2026)
- Cyber Security Agency of Singapore: Alert AL-2026-157 on active PHP2Shell exploitation of network and security products, affected products and advice (updated Nov 6, 2026)
- Fortinet PSIRT FG-IR-26-186: PHP2Shell patches for FortiSOAR and FortiSOAR PaaS, impact limited to denial of service, FortiDDoS under investigation (updated Nov 5, 2026)
