ID :ISA-2026-130
Critical alertActiveCVSS 9.2/10IservicesCSIRT

Critical Remote Code Execution Vulnerabilities in PHP Core ("PHP2Shell" - CVE-2026-109618 & CVE-2026-109619)

Executive Summary

Two critical core-level Remote Code Execution (RCE) vulnerabilities-collectively known as PHP2Shell-have been identified in the PHP core engine (CVE-2026-109618 and CVE-2026-109619). These vulnerabilities allow unauthenticated remote attackers to execute arbitrary code on vulnerable web servers running PHP applications (including WordPress, Drupal, Magento, Laravel, and custom stacks). The vulnerabilities stem from memory mismanagement and improper state handling during abnor...

Published on October 21, 2026 at 01:00 AM by Iservices Csirt36 views

Description

Technical context and vulnerability details

PHP is the dominant server-side web programming language powering a vast majority of the world's web applications and content management systems.

The PHP security team issued urgent updates addressing two critical flaws residing in the core request handling and memory cleanup routines:

  • CVE-2026-109618 (Critical - CVSS v4.0: 9.2): Out-of-Memory (OOM) Heap Corruption leading to RCE. This flaw occurs during abnormal request termination contexts, such as when an execution exceeds the configured memory_limit. Because PHP historically relies on longjmp() to abruptly abort execution rather than cleanly unwinding the call stack, internal C functions interrupted midway through constructing complex data structures fail to invoke destructors or roll back bookkeeping. Consequently, when the cleanup routine executes, it assumes all structures are in a consistent state, resulting in an uninitialized pointer dereference (CWE-824) and stale heap corruption that can be weaponized for remote code execution.

  • CVE-2026-109619 (Critical - CVSS v4.0: 9.2): Use-After-Free (UAF) via Fatal Error Handling. This flaw is a use-after-free vulnerability triggered during fatal errors or multipart form parsing (notably involving the upload progress tracking callback php_session_rfc1867_callback under session.upload_progress.enabled). Leftover memory state from an abruptly aborted request points to freed memory chunks, which can subsequently be reached and abused by subsequent requests processed by the same worker process or thread.

These vulnerabilities are actively targeted in the wild following public proof-of-concept leaks. Because they reside in the PHP core engine itself, patching application-level code or plugins is insufficient: the underlying PHP runtime binary must be upgraded and all worker pools restarted.

Potential Risks & Impact

Potential consequences upon exploitation

  • Remote arbitrary code execution (RCE) without prior authentication;
  • Full compromise of underlying server and host operating system;
  • Unauthorized exfiltration, modification, or deletion of databases and files;
  • Deployment of persistent webshells, backdoors, and ransomware;
  • Complete loss of confidentiality, integrity, and availability.

Affected systems

Products, components and targeted versions

  • PHP 8.5.x versions prior to 8.5.12;
  • PHP 8.4.x versions prior to 8.4.27;
  • PHP 8.3.x versions prior to 8.3.36;
  • PHP 8.2.x versions prior to 8.2.35;
  • All legacy End-of-Life (EOL) versions (including PHP 8.1, 8.0, 7.4, 7.x, and 5.x) which do not receive official public upstream patches.

Recommended Remediations & Actions

Immediate actions and recommended mitigations

  • Immediate Runtime Upgrade: Upgrade PHP runtimes across all production, staging, and development environments to the latest patched releases:
    • PHP 8.5 -> upgrade to 8.5.12 or later;
    • PHP 8.4 -> upgrade to 8.4.27 or later;
    • PHP 8.3 -> upgrade to 8.3.36 or later;
    • PHP 8.2 -> upgrade to 8.2.35 or later.
  • Mandatory Process Restart: Upgrading binaries alone is insufficient. System administrators must immediately restart all PHP worker services (systemctl restart php-fpm, systemctl restart apache2, systemctl restart nginx, or restart application containers) to ensure all in-memory workers flush vulnerable state.
  • Temporary Mitigation (if patching cannot be immediately completed):
    • Disable upload progress tracking in php.ini, .user.ini, or pool configuration by setting: session.upload_progress.enabled = Off
    • Configure Web Application Firewalls (WAF) and reverse proxies to inspect and throttle anomalous multipart/form-data POST requests to endpoints that do not accept file uploads.
  • EOL Systems: Migrate legacy PHP installations (7.x / 8.0 / 8.1) immediately to an actively supported LTS version, or apply vendor-provided Extended Lifecycle Support (ELS) patches.
  • Incident Response & Hunting: Inspect web server access logs and error logs for anomalous fatal memory spikes, repeated OOM errors, and unauthorized webshell creation.

Advisory Specifications

ISA-2026-130
CVSS scoreCRITICAL
9.2/ 10.0
0.0 (Low)5.0 (Med)10.0 (Crit)
PriorityCritical
StatusActive
Typesecurite
Published onOctober 21, 2026 at 01:00 AM
OrigineIservicesCSIRT
Audience36 views

CSIRT Emergency Response

Is your organization affected or do you suspect an incident? Our security experts are available to assist.

Report an incident

Get our alerts by email

Subscribe to receive our security alert bulletins and Iservices news straight to your inbox.

Ready to Work With Us?

Join hundreds of satisfied clients who trust Iservices with their technology needs. Let's discuss how we can help transform your business.

Get our alerts by email

Subscribe to receive our security alert bulletins and Iservices news straight to your inbox.