Your developers may not write PHP. Your suppliers may still ship it.
PHP2Shell is a runtime problem that can reach well beyond the website team. PHP released fixes for CVE-2026-109618 and CVE-2026-109619 on October 21, 2026, rating both Critical, CVSS v4.0 9.2. The relevant PHP fix must reach the software actually serving requests, including runtimes embedded in supplier products. PHP security advisory.
Cloudflare reports affected pre-fix releases extend back to PHP 5.4. Prioritize exposed web-serving PHP across your estate, not just applications running a recent branch. Cloudflare technical overview.
Detection resources updated October 29, 2026. Start with existing endpoint events or Sysmon for Linux XML. The incident and patch guidance below retain their original October 21 scope.
Start with the running runtime
Use the fixed release for the branch you run, or a supplier-confirmed package containing both fixes:
Swipe tables horizontally to see all columns.
| PHP branch | First upstream fixed release |
|---|---|
| 8.2 | 8.2.35 |
| 8.3 | 8.3.36 |
| 8.4 | 8.4.27 |
| 8.5 | 8.5.12 |
PHP 8.1 and earlier are upstream end-of-life. Move to a supported branch or obtain a verified vendor/LTS fix; PHP has also provided exceptional minimal source backports for 7.4, 8.0, and 8.1. A backport is not renewed upstream support. Distribution package numbers may differ, so verify the supplier advisory rather than comparing the public banner alone. PHP release guidance.
Patch every relevant instance, rebuild and redeploy affected images, and restart or replace the PHP workers. Verify the web-serving process, not just php -v in a shell: CLI PHP, FPM pools, containers, and different application sites can load different installations.
Include the PHP your suppliers operate
Expand the inventory beyond repositories and developer language surveys. Check packaged business applications, CMS and commerce platforms, hosting/control panels, container base images, appliance web interfaces, outsourced portals, and managed services.
Ask each relevant supplier which deployed product versions embed or invoke web-serving PHP, whether both CVEs are fixed, which package or image includes the fix, and when that release will reach your tenant or estate. For a hosted service, request rollout confirmation rather than attempting to patch a service you do not control.
The closure chain is PHP fix → supplier release → your deployment → verified running workers. Track the owner and evidence at every handoff. “Our vendor is aware” is not the same as “our affected instances are fixed.”
For scale, W3Techs reported PHP on 69.3% of websites whose server-side language it could identify, while BuiltWith listed about 24 million live PHP websites when checked on October 21. Those are different measurements, not counts of vulnerable systems, and neither replaces your internal or supplier inventory. W3Techs, BuiltWith.
THE SUPPLIER PATCH CHAIN
An upstream patch is not the finish line
- 01PHP fixUpstream security release
- 02Supplier releaseFixed product or image
- 03Your rolloutEvery applicable instance
- 04Running workersRestarted and verified
Understand the failure in plain language
CVE-2026-109618 concerns cleanup after memory exhaustion. PHP can stop work while internal request data is only partly initialized; cleanup can then use that invalid state. The advisory confirms unauthenticated remote code execution with the web worker's privileges on Apache mod_php. PHP OOM advisory.
CVE-2026-109619 concerns state left between requests. A worker can retain a reference to memory belonging to an ended request. Another request handled by that same worker can encounter the stale reference before normal initialization clears it. Demonstrated session-lifecycle exploitation includes both mod_php and PHP-FPM, with additional application conditions for FPM. FPM is not a blanket exemption. PHP stale-state advisory.
The impact includes code execution, data exposure, and denial of service. Sensitive process memory is also at risk, so include confidentiality in the response, not only server takeover. Cloudflare impact analysis.
Do not wait for an application-specific flaw or an authenticated session to prioritize exposed PHP. Cloudflare reports attack traffic and watchTowr reports active exploitation attempts. Cloudflare, watchTowr.
If patching must wait
Restrict or remove unpatched exposure wherever practical. Put access control before the PHP request handler, not only inside the application. The NSA recommends taking systems offline when an immediate update is not feasible; UK NCSC says to consider it if temporary mitigations cannot be applied or would take too long. NSA advisory, UK NCSC guidance.
Temporary PHP settings affect specific paths, not the whole issue. Disabling session upload progress, and disabling PHP 8.5 fatal-error backtraces, remove demonstrated stale-state paths. They do not close every lifecycle variant or fix the separate OOM bug. Apply such settings administratively before request parsing and restart workers; application-level toggles can be too late. The technical companion separates these controls by CVE.
For the OOM path, PHP recommends a low post_max_size: 8M without required file uploads, or 32M with uploads, keeping upload_max_filesize lower. PHP also documents memory_limit=-1 as a partial mitigation. Removing that per-request cap increases resource-exhaustion risk, so pair it with tested frontend limits and an availability plan. These measures reduce specific paths; patching is the complete solution. PHP mitigation guidance.
Keep relevant managed WAF protections enabled and confirm their effective action, exceptions, body-inspection limits, and routing. Close direct-origin bypasses while preserving legitimate operations. Cloudflare's response-phase protection can stop a matching response reaching a requester; that does not mean the request never reached PHP or that origin-side actions were undone. Cloudflare protection details, response-phase boundaries.
Hunt for consequences as well as requests
Start with an affected service and an exposure window, then ask what reached its origin and what the worker did afterward. Preserve access, proxy/WAF, PHP error, endpoint, file-integrity, and outbound-network records. Use UTC timestamps, request IDs, workload identity, and worker/process context where available.
- Error patterns: unusual memory-exhaustion errors, worker crashes, restarts, or repeated fatal errors near unfamiliar request activity. Annotate patch rollout times: the updated runtime can terminate a worker by design at its hard-OOM threshold. PHP OOM change.
- Unexpected execution: PHP or a web service spawning shells, download tools, interpreters, or discovery utilities outside its normal workflow. Correlate the process tree with the request and application owner.
- Changed state: unfamiliar executable files in web or writable directories, new persistence, altered configuration, or unexpected outbound connections. Preserve artifacts before cleanup.
Read hunt results in context. These examples surface investigation leads, not PHP2Shell-specific proof. Memory disclosure and in-process activity can leave no child process or dropped file; assess the exposed runtime and available evidence even when a hunt is quiet.
Give leaders evidence of closure
Maintain three lists: verified fixed, temporarily contained with an owner and expiry, and unresolved supplier or deployment dependency. For each service, record the deployed build, the advisory or backport reference, worker rollout evidence, relevant WAF/origin controls, and investigation status.
For services reachable while vulnerable, assess possible exposure of application secrets and downstream access even without process or file evidence. Prioritize precautionary rotation where exposure is plausible or telemetry is insufficient, using the secrets available to that worker and your incident-response assessment. Confirmed suspicious execution or access requires incident response; patch completion does not close that investigation.
Put the response into practice
Use the SOC companion to assess impact and investigate activity. Download the detection examples and tests, and use the supplier questions to obtain fixed-build and rollout evidence. The refreshed pack leads with standard Linux Sigma and native Microsoft, CrowdStrike, Sophos, Splunk, and Sumo Logic routes. Choose your source and read the inline queries. Specialty YARA, Snort-style content rules, and earlier custom adapters remain in the advanced section.
Find the runtime. Follow the supplier chain. Verify the running fix.
Prepared by Deception Check, October 21, 2026.
