PHP2Shell: Anatomy of a Critical Runtime Crisis and What It Means for the CMS Ecosystem
On 21 October 2026, the PHP project shipped emergency security releases that closed two of the most severe vulnerabilities the language has faced in years. Tracked as CVE-2026-109618 and CVE-2026-109619 and widely referred to as PHP2Shell , both flaws carry a CVSS v4.0 score of 9.2 and enable unauthenticated remote code execution in the PHP runtime itself. This is not a plugin vulnerability. It is not a theme flaw. It is not even a WordPress, Drupal, or Magento bug. It is a memory-safety failure deep inside the interpreter that powers roughly 70% of the web whose server-side language is known. For application architects and CMS operators, the distinction is fundamental: updating the application layer does nothing. The runtime must be patched. What Exactly Broke CVE-2026-109618 – RCE via OOM Corruption PHP uses longjmp() to abort request handling when memory limits are hit. In certain contexts—particularly during multipart form parsing—request memory can exist in a partially initialize...