National Cybersecurity Threat Intelligence Advisory · October 21, 2026

PHP2Shell: Critical PHP Zero-Day Security Advisory

Two critical PHP vulnerabilities threaten web-facing applications with unauthenticated remote code execution. Executive leadership should authorize urgent inventory, security updates, worker restarts and compromise assessment.

CVE-2026-109618CVE-2026-109619CVSS v4.0: 9.2 Critical (each)Advisory v2.0 · 21 Oct 2026
RECOMMENDED RESPONSE: P1 — CRITICAL / URGENT
Start remediation immediately; target 24-hour completion for exposed production environments. Escalate to P0 where compromise is suspected or confirmed, or an active incident threatens essential services. Vendor states that only updating provides a complete solution.
01 / Board-level intelligence

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.

2
Critical CVEs

Separate flaws, both potentially enabling unauthenticated remote code execution.

9.2
CVSS v4.0 each

PHP-assigned critical severity; score is not a count of attacks.

P1
Advisory priority

Urgent enterprise patching; P0 for confirmed incidents.

4
Patched release lines

8.2.35 · 8.3.36 · 8.4.27 · 8.5.12

Evidence discipline: Internet-wide counts of vulnerable PHP sites are not equivalent to confirmed victims. This bulletin does not invent compromise counts, affected-person totals or numeric attack forecasts.
02 / Risk taxonomy

American CIO Priority-Level Legend

P0EmergencyImmediate containment and incident response; confirmed or imminent critical business impact.
P1Critical / UrgentBegin immediately; target remediation within 24 hours.
P2HighPrioritize remediation within 72 hours.
P3ModerateRisk-based remediation within 7–14 days.
P4Low / InformationalAddress through planned maintenance.

These are American CIO suggested operational response targets, not CISA-mandated deadlines. Adjust for exposure, observed attacks, business criticality and compensating controls.

03 / Verified impact vs. exposure

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.

Not established
Confirmed US victim organizations

No independently validated national victim count used in this report.

Not established
Confirmed worldwide victims

Do not extrapolate from proof-of-concept activity or attack traffic.

Unquantified
Potentially vulnerable websites

Exposure requires version, SAPI, patch/backport and deployment validation.

Unquantified
Projected affected businesses

No reliable incident-rate denominator or conversion model available.

Forward-looking assessment

HorizonConservative scenarioBaseline scenarioSevere escalation scenario
24 hoursUnpatched exposure persistsScanning and defensive patching continueTargeted compromise of exposed assets is possible
72 hoursOrganizations reduce exposure through upgradesPatch coverage remains unevenCompromise investigations and operational disruption may increase
7 daysMost managed environments remediateLegacy and unmanaged hosts lagPersistent access remains after late patching
30 daysResidual exposure concentrated in legacy systemsLong-tail vulnerability management continuesDelayed 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.

04 / Technical intelligence

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.

05 / Execution

24-Hour Emergency Response Plan

WindowActionOwnerCompletion evidence
0–2 hoursActivate emergency change control; identify Internet-facing PHP services and critical applicationsCISO / InfrastructureScoped asset inventory and accountable owners
0–4 hoursCheck installed/runtime PHP versions and vendor patch status; preserve relevant logsPlatform / SOCRuntime evidence, advisory mapping, log retention confirmation
2–12 hoursDeploy patched PHP packages or verified vendor backports; test application compatibilityEngineering / Change managementChange tickets and tested release evidence
2–16 hoursRestart Apache, PHP-FPM and all long-running workers; recycle containers and images as appropriateOperationsRunning process versions and deployment attestations
4–24 hoursHunt for suspicious requests, webshells, abnormal process execution, outbound connections and credential misuseSOC / IRDetection results, incident tickets and escalation decisions
By 24 hoursProvide executive closure report with remaining exceptions, exposure and compensating controlsCISO / CIOSigned 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.
06 / Enterprise impact

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.
07 / Research transparency

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.

  1. PHP Project — Critical remote code execution vulnerabilities, update now (primary; October 21, 2026).
  2. PHP Project — Downloads and supported security releases (primary; October 21, 2026).
  3. NIST NVD — CVE-2026-109618 (primary vulnerability database).
  4. NIST NVD — CVE-2026-109619 (primary vulnerability database).
  5. Qualys — PHP2Shell security research and attack traffic (secondary; October 21 update).
  6. 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.