# The first four hours after a zero day disclosure run in a fixed order, shown here hour by hour on PHP2Shell

Guide, 19 Nov 2026, read 19 Nov 2026

**The short answer.** In the first four hours after a zero day disclosure, extract seven facts from the advisory, check exploitation signals beyond the CISA catalog, find the web-facing binary on every host, and apply the vendor's mitigation order. The PHP2Shell release of 21 Oct 2026 is worked from the 14:00 UTC release to hour four.

## PHP2Shell is the running example: attack tools were in use about ten hours before the fix

The PHP release of 21 Oct 2026 (CVE-2026-109618 and CVE-2026-109619, nicknamed PHP2Shell) allows unauthenticated remote code execution in PHP that serves web requests. Fastly's telemetry, published on 23 Oct 2026, shows a named tool at 03:59 UTC on 21 Oct, about ten hours before the coordinated release at 14:00 UTC, and CISA listed both bugs on 26 Oct. None of that was visible during the four hours below. The steps for the whole 72 hours on this asset type are in the [application runtime playbook](/playbooks/application-runtime/).

A team that read the 19:30 pre-announcement on 20 Oct had 18 hours 30 minutes of warning. A team that first read the advisory at 14:00 started about ten hours after the first named tool.

## Hour 0 to 1: write seven facts from the advisory into the record

The security lead opens the vendor advisory, GHSA-w8hw-w9fx-j79w, and fills seven fields. The record leaves a one-line answer per field, each with the time it was read.

| Field | PHP2Shell, from the advisory |
| --- | --- |
| Disclosure time | Release 21 Oct 2026 at 14:00 UTC; GitHub advisory published 21 Oct |
| Affected | PHP 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27, 8.5 before 8.5.12 |
| No fix exists for | PHP 8.1 and older (no upstream fix) |
| Exposed through | Apache mod_php (rated highest by PHP), PHP-FPM, php-cgi, FrankenPHP, LiteSpeed |
| Workaround | None that is complete: updating is the only complete mitigation. memory_limit=-1 with a restart of every worker is partial |
| Exploitation statement | The advisory confirms remote code execution over HTTP against mod_php and says nothing about attacks in the wild |
| Companion flaw | CVE-2026-109619 comes from the same release; the advisory says to follow the remediation advice for both |

## Hour 1 to 2: an empty catalog is not a clear signal, so read two outside sources and your own logs

A security lead who searched the CISA catalog at 15:00 on 21 Oct found nothing, because the listing came on 26 Oct. The advisory has no attack statement, so the signals come from elsewhere. Record the result of each with a time.

Fastly published the request shape on 23 Oct, so on 21 Oct a team had only the first source below and its own logs. Search back to the pre-announcement of 20 Oct, 19:30 UTC.

- CISA's alert of 21 Oct, Critical Vulnerabilities in PHP Require Immediate Patching. It names the fixed releases, tells organizations to inventory every installation, including bundled copies, and says to monitor for PHP worker processes launching shells or downloading tools. CISA added a SIGMA detection rule on 23 Oct.
- Fastly's report of 23 Oct, which names the request shape of the most widespread exploit kit: POST to / or /index.php, Content-Type multipart/form-data with the fixed boundary B7kQpoc618, a fixed-size body, a minimal header set, raw IP addresses as targets, one or two requests per host. Fastly says the boundary string is the most reliable separator; User-Agent strings (php2shell-109618 here), source IPs and body sizes go stale within a day.
- Your own edge logs, searched for that shape. Success is not visible at the edge: success shows at the origin, in PHP-FPM and Apache error logs (worker crashes such as AH00051 child exit entries) and in outbound connections from PHP workers. A hit changes the plan: start the compromise check on that host before you patch or rebuild it, and keep the evidence first.
- Look-alikes, ruled out before anything is counted. Fastly measured 98.6% and 99.9% of two circulating PHP2Shell signatures (chunked multipart with no Content-Length, bodies padded with the letter A) as React2Shell traffic, which carries a Next-Action header that PHP traffic never does. A WordPress kit whose boundary starts ----wp2shell is a separate July 2026 campaign.

## Hour 2 to 3: find the web binary, not the command-line tool

Platform engineering answers where the vulnerable component serves requests. A command-line tool on a host can report a different version from the one behind the web server, so the check runs against the running service. For PHP that means the web server API (SAPI).

Group the answer by what the host does, with the server type the vendor rates highest first (PHP rates Apache mod_php highest). A version with no upstream fix is a group of its own: the answer is a distributor backport or an upgrade.

- Running web servers: ps -ef | grep -Ei 'php-fpm|php-cgi|frankenphp|lsphp|httpd|apache2' | grep -v grep. Whether Apache loads mod_php: apachectl -M | grep -i php (apache2ctl -M on Debian and Ubuntu). Packages: dpkg -l 'php*' 'libapache2-mod-php*' or rpm -qa 'php*'. A host that runs PHP only from the command line, for cron jobs, drops out of web scope.
- Version of the web binary: php-fpm -v or php-cgi -v; for mod_php, php -v after confirming the module. Distributions backport fixes without changing the number, so ask the package: rpm -q --changelog php | grep -i 109618 or apt changelog php8.3 | grep -i 109618, and the same with 109619. A version below the fixed release can still be patched. Fixed upstream releases are 8.2.35, 8.3.36, 8.4.27 and 8.5.12; 8.1 and older have none.
- Check every container image and every product that bundles the component.
- Leave one line per host or image: server type, version, changelog hit yes or no, reachable from the internet yes or no, owner.

## Hour 3 to 4: apply the vendor's mitigation order and write each cost down

Patching needs a canary first. While it runs, apply the options in order of how much they remove, and write each into the record with its cost, its owner and the time it will be reviewed. The options below are PHP's and CISA's own, except the frontend refusal, which is this site's rule for applications with no uploads.

| Option | What to set | Stated cost or limit | Source |
| --- | --- | --- | --- |
| 1. Update | PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12, or the distribution's patched package; restart every worker | A staging test first; the fix changes out-of-memory handling. A package install does not replace running workers | PHP advisory GHSA-w8hw-w9fx-j79w: the only complete mitigation |
| 2. Partial setting change | CVE-2026-109618: memory_limit=-1 as an admin value (php_admin_value[memory_limit] = -1 in an FPM pool; php_admin_value memory_limit -1 in Apache), then restart every worker. CVE-2026-109619: session.upload_progress.enabled=0, and on PHP 8.5 fatal_error_backtraces=0 | A runaway script can use all host memory; upload progress stops. Partial: a failed mmap() can still reach the vulnerable path. Do not use RLIMIT_AS or RLIMIT_DATA, which make mmap() fail | PHP advisories GHSA-w8hw-w9fx-j79w and GHSA-6wmf-4rv5-p3rp |
| 3. Refuse at the frontend | Keep post_max_size conservative and enforce the decoded size at the frontend. Where the application has no uploads, refuse multipart before PHP, for example in nginx: if ($content_type ~* "^multipart/form-data") { return 415; } | File uploads and multipart forms stop working | PHP advisory (size limits); the 415 rule is this site's |
| 4. WAF rule | A rule for both CVEs, as a stopgap; Fastly Next-Gen WAF has one | Partial. Fastly warns that circulating IP block lists include VPN exits, Tor exits and residential addresses carrying ordinary traffic | CISA alert; Fastly report |
| 5. Take it offline | Systems that cannot be updated, and PHP 8.1 and earlier | The service is down; accept in writing with an expiry date if it must stay up | CISA alert |

## Hour 4: log one decision per group and set the next update time

Close the first window with a decision per group, an owner and a review time. The entries below show the form; the group names are examples to replace with your own. The log feeds the board brief and the 72-hour review.

| Group (example) | Decision at 18:00 UTC | Owner | Review |
| --- | --- | --- | --- |
| Public web tier on Apache mod_php | Patch in rings starting tonight; memory_limit=-1 until the fixed build is verified | Platform engineering | 22:00 UTC, next update |
| Internal tools on PHP-FPM | Patch within 24 hours | Application owner | 22 Oct 14:00 UTC |
| Hosts on PHP 8.1 | Take offline, or accept in writing with an expiry date | Executive | Expiry date required |

## Five situations where the first four hours change

The PHP order assumes a fix, a workaround and no earlier compromise. These cases from the site's CVE data break one of those assumptions.

- Exploitation began before the advisory. BeyondTrust's CVE-2026-102764 was used from 29 Aug 2026 and disclosed on 15 Oct. Start with the compromise check: the actor deleted local logs, so off-box syslog is often the only record, and BeyondTrust and Mandiant advise rebuilding from a clean image rather than cleaning in place.
- No workaround exists. Palo Alto lists none for PAN-OS CVE-2026-0322, and Cisco lists none for ISE CVE-2026-76460. Hour 3 becomes access restriction: a jump box for the PAN-OS management interface, which Palo Alto rates 8.5 instead of 8.6, so it lowers risk only a little, and infrastructure access control lists for ISE.
- The vendor withholds details. BeyondTrust held back technical details while self-hosted appliances were patched, and Mandiant notes the actor rotates infrastructure per victim. Hunt for behavior (unrecognized privileged sessions, scripts in web directories), not for one victim's indicators.
- Some copies are patched for you. BeyondTrust patched its SaaS instances automatically on 8 Oct 2026; self-hosted appliances needed action. Ask the vendor which copies it handled.
- A version has no fix. Cisco ISE 3.0 is past software maintenance and has no patch in the 16 Sep 2026 advisory; the answer is a move to a supported release.

## Related pages

- [Out-of-band patch: how to run one without breaking production](/guides/out-of-band-patch/)
- [Zero day response plan: the complete template with owners, triggers and a drill](/guides/zero-day-response-plan/)
- [The board brief by noon: template, interim note and a filled brief for Cisco ISE](/guides/board-brief-by-noon/)

## Sources

- PHP security advisory GHSA-w8hw-w9fx-j79w: https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w (read 19 Nov 2026)
- Fastly: PHP2Shell timeline, telemetry and indicators (23 Oct 2026): https://www.fastly.com/blog/how-fastly-detected-and-built-a-coordinated-response-to-php2shell (read 19 Nov 2026)
- CISA alert: Critical Vulnerabilities in PHP Require Immediate Patching: https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching (read 19 Nov 2026)
- BeyondTrust: ARMORY CASTLE and BT26-05: https://www.beyondtrust.com/blog/entry/bt26-05 (read 19 Nov 2026)
- Mandiant: ARMORY CASTLE Exploits BeyondTrust: https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-beyondtrust (read 19 Nov 2026)
- Palo Alto Networks advisory CVE-2026-0322: https://security.paloaltonetworks.com/CVE-2026-0322 (read 19 Nov 2026)
- Cisco advisory cisco-sa-ISE-ABP-VNSW7Tn5: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ISE-ABP-VNSW7Tn5 (read 19 Nov 2026)
- CISA Known Exploited Vulnerabilities catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://zerodayplaybook.com/guides/what-to-do-when-a-zero-day-is-disclosed/
