Executive Threat Overview
The PHP project identifies two distinct memory-state vulnerabilities affecting web-serving PHP runtimes. Risk is particularly acute for Apache mod_php, where a demonstrated attack can trigger before application code runs. Other PHP serving modes also require remediation. PHP security advisory.
Separate flaws, both potentially enabling unauthenticated remote code execution.
PHP-assigned critical severity; score is not a count of attacks.
Urgent enterprise patching; P0 for confirmed incidents.
8.2.35 · 8.3.36 · 8.4.27 · 8.5.12
American CIO Priority-Level Legend
These are American CIO suggested operational response targets, not CISA-mandated deadlines. Adjust for exposure, observed attacks, business criticality and compensating controls.
Current Affected & Projected Affected
Reporting as of October 21, 2026. Published exploitation claims and scanning observations are not the same as a validated count of compromised organizations.
No independently validated national victim count used in this report.
Do not extrapolate from proof-of-concept activity or attack traffic.
Exposure requires version, SAPI, patch/backport and deployment validation.
No reliable incident-rate denominator or conversion model available.
Forward-looking assessment
| Horizon | Conservative scenario | Baseline scenario | Severe escalation scenario |
|---|---|---|---|
| 24 hours | Unpatched exposure persists | Scanning and defensive patching continue | Targeted compromise of exposed assets is possible |
| 72 hours | Organizations reduce exposure through upgrades | Patch coverage remains uneven | Compromise investigations and operational disruption may increase |
| 7 days | Most managed environments remediate | Legacy and unmanaged hosts lag | Persistent access remains after late patching |
| 30 days | Residual exposure concentrated in legacy systems | Long-tail vulnerability management continues | Delayed discoveries and secondary impacts remain possible |
These are qualitative planning scenarios, not measured incident projections or probability forecasts. Numerical estimates are withheld because verifiable counts of vulnerable hosts, attack success rates and incident reporting coverage are insufficient.
Vulnerability Analysis
CVE-2026-109618
RCE via out-of-memory corruption
An allocation failure can interrupt initialization of internal request data. Cleanup may subsequently interpret partially initialized data as valid, enabling memory corruption and possible code execution.
Recommended: P1 for exposed systems; P0 when compromise is established.
CVE-2026-109619
RCE via stale global state
Request-owned state can survive after backing memory is freed. Subsequent requests handled by the same worker may reuse stale state, with potential code execution or memory disclosure.
Recommended: P1 for exposed systems; P0 when compromise is established.
Which PHP deployments are in scope?
PHP identifies web-serving deployments including PHP-FPM, Apache mod_php, php-cgi, FrankenPHP and LiteSpeed. Apache mod_php warrants particularly urgent attention. Determine actual runtime versions and vendor backports for each service, not only the command-line PHP version.
What about temporary configuration mitigations?
PHP documents risk-reduction measures for specific paths, including request-size controls, memory-limit changes and disabling session upload progress. These are incomplete and can introduce availability tradeoffs. They do not replace patching. Consult the official advisory before changes.
Does patching prove a host was never compromised?
No. Updating eliminates known vulnerable code paths but does not remove webshells, stolen credentials, malicious scheduled tasks or other attacker persistence. Investigate indicators before declaring recovery complete.
24-Hour Emergency Response Plan
| Window | Action | Owner | Completion evidence |
|---|---|---|---|
| 0–2 hours | Activate emergency change control; identify Internet-facing PHP services and critical applications | CISO / Infrastructure | Scoped asset inventory and accountable owners |
| 0–4 hours | Check installed/runtime PHP versions and vendor patch status; preserve relevant logs | Platform / SOC | Runtime evidence, advisory mapping, log retention confirmation |
| 2–12 hours | Deploy patched PHP packages or verified vendor backports; test application compatibility | Engineering / Change management | Change tickets and tested release evidence |
| 2–16 hours | Restart Apache, PHP-FPM and all long-running workers; recycle containers and images as appropriate | Operations | Running process versions and deployment attestations |
| 4–24 hours | Hunt for suspicious requests, webshells, abnormal process execution, outbound connections and credential misuse | SOC / IR | Detection results, incident tickets and escalation decisions |
| By 24 hours | Provide executive closure report with remaining exceptions, exposure and compensating controls | CISO / CIO | Signed risk register and remediation dashboard |
Seven-day stabilization
- Reconcile CMDB, web application inventory, cloud images and vendor-managed hosting coverage.
- Recheck patched runtime from the actual web-serving process; validate vendor backports.
- Review EDR, WAF, application, authentication and network telemetry; distinguish suspicious activity from verified indicators.
- Rotate credentials and secrets if exposure or compromise evidence justifies it.
- Validate backups, restoration capability and business-critical application workflows.
- Document exceptions and retire unsupported PHP branches or move to maintained vendor-supported builds.
Business, Regulatory & Sector Exposure
Organizations using affected PHP runtimes may face unauthorized code execution, sensitive-data exposure, ransomware staging, disruption, forensic expense and reputational harm. Relative urgency depends on Internet exposure, data sensitivity, operational criticality and patch status—not merely industry classification.
Higher-consequence environments
- Healthcare and emergency services: patient care continuity and protected information
- Financial services and commerce: payment workflows, identity and transaction data
- Government and public safety: service availability and sensitive records
- Hosting providers: concentration risk across multiple tenants
Governance implications
- Determine applicable HIPAA, GLBA, PCI DSS and state breach notification requirements based on actual facts and scope.
- Preserve incident evidence and coordinate legal, insurance and contractual notifications when warranted.
- Quantify internal exposure, not unsupported nationwide financial-loss totals.
Sources, Evidence & Methodology
Primary vendor advisories establish vulnerability mechanism and remediation. Secondary research provides context; attack-traffic reporting alone does not establish unique compromised victims.
- PHP Project — Critical remote code execution vulnerabilities, update now (primary; October 21, 2026).
- PHP Project — Downloads and supported security releases (primary; October 21, 2026).
- NIST NVD — CVE-2026-109618 (primary vulnerability database).
- NIST NVD — CVE-2026-109619 (primary vulnerability database).
- Qualys — PHP2Shell security research and attack traffic (secondary; October 21 update).
- UK NCSC — Critical security issue affecting PHP (national authority; October 21, 2026).
Verified on October 21, 2026. High confidence: official PHP CVEs, vulnerability descriptions, severity and fixed versions. Moderate confidence: public reporting of hostile probing. Unknown: unique victim totals, US enterprise counts and defensible numeric 30-day projections. Update this publication when authoritative data becomes available.