AivexaNewsSearch
AI news for builders and product teamsChecked every hour

Today's PHP Security Release, and How We're Strengthening PHP Security

Collected Oct 21, 2026

PHP released security updates across its 8.x branches on October 21, addressing two remote code execution vulnerabilities. Running PHP without these updates leaves a system exposed, because exploits have been circulating since the previous evening. The accelerated schedule followed a breakdown in the coordinated disclosure process: according to the PHP Foundation, the two CVE identifiers surfaced on forums and social media around 15:00 UTC on Tuesday, October 20, accompanied by an incorrect release time and an inflated CVSS score of 10.0. The actual severity score is 9.2. No technical details leaked at that stage.

The project responded by publishing its pre-announcement at 19:30 UTC that day and pulling the release forward from October 22 at 14:00 UTC to October 21 at 14:00 UTC. Around 20:00 UTC, security firm Calif, one of the organizations that had reported the issues, mistakenly published a video showing its proof of concept working against several targets and exposing a few limited additional details. The video was deleted, but copies spread on social media, which sped up development of further proof-of-concept exploits and increased their circulation on October 21.

The disclosure history, as described by the team that found the original flaw, began in August. Wiz Research identified the first PHP vulnerability on August 19 using its Wiz Atlas tooling alongside Gemini 4 Argon and GPT-5.6 Sol. Unauthenticated remote code execution was confirmed against Drupal on August 20 and against WordPress on August 21. Wiz reported the vulnerabilities to the PHP security team on August 24. PHP acknowledged the reports on September 21 and started work on a coordinated fix, with patched releases and public disclosure both landing on October 21.

Context worth having: PHP powers a large share of the web, including the WordPress and Drupal content management systems named here, so an unauthenticated RCE in the runtime is a serious exposure for shared hosts and any application that accepts untrusted input. A CVSS score of 9.2 is rated critical; the leaked 10.0 figure overstated the severity. The gap between the leak and the patch gave attackers a head start, which is precisely the risk coordinated disclosure is designed to manage. This suggests sites that patched within hours of release had little exposure to the earliest public proofs of concept, while slow-moving deployments likely did not.

Why it matters: anyone operating PHP 8.x, directly or through a CMS such as WordPress or Drupal, should treat this as urgent and upgrade to the patched release for their branch now. The leak-driven timeline means exploit code exists in the wild, so the usual staging and test windows carry real risk. For product teams, this is also a reminder that embargo timing depends on every party in the loop; a single premature video from a reporting firm can compress the window between disclosure and exploitation by days.

Read at Simon Willison

Based on reporting from the original publisher. Visit the source for full context and later updates.

Publisher excerpt

Today's PHP Security Release, and How We're Strengthening PHP Security If you're running anything on PHP it's vital you upgrade - today's updates (across the entire PHP 8.x line) address two remote code execution holes, and there have been exploits circulating since last night, thanks to a leak in the coordinated disclosure process. This post from the PHP Foundation explain what went so wrong: On Tuesday, October 20th, at around 15:00 UTC, the two CVE IDs began circulating on online forums and social media. They ca