PHP security team ships patches for two 9.2-rated flaws
The PHP security team scheduled emergency patches for two critical vulnerabilities rated 9.2 on 21 October 2026 at 14:00 UTC, prompting UK, EU and Australian agencies to urge websites offline if they cannot update.
Photo: BBC NewsKey points
PHP security team scheduled emergency patches for two critical vulnerabilities rated 9.2, urging sites to update or go offline.
The PHP security team scheduled emergency patches for two critical vulnerabilities in the language on 21 October 2026 at 14:00 UTC, which is 10:00 AM Eastern. Each flaw is rated 9.2 under CVSS v4.0, the Common Vulnerability Scoring System used to grade security bugs on a 0 to 10 scale. The team urged administrators to install the updates as soon as they become available.
The vulnerabilities matter because PHP runs on servers behind a large share of the internet, including WordPress, Drupal, Joomla and Magento sites, shared hosting platforms and control panels, according to cyber-security company Huntress. The UK's National Cyber Security Centre, the European Union's CERT-EU and Australia's cyber agency all urged users to apply the fixes as soon as they are released, or to take systems offline if they cannot.
What the advisory changed
The PHP security team published an advisory announcing the release plan and sent a notice to its ANNOUNCE mailing list. The team wrote that it reserves the right to release earlier should details of either vulnerability become public or should evidence of active exploitation appear. Developers have not disclosed which PHP versions are affected or how the flaws can be exploited, and said full technical details will come with the updates.
Security researchers at watchTowr identified the vulnerabilities as CVE-2026-109618 and CVE-2026-109619, describing them as remote code execution flaws that let attackers run their own code on affected servers. watchTowr chief executive Benjamin Harris said the vulnerabilities were previously under embargo and due for release on Thursday at 11 am ET, but information leaked ahead of that schedule. He said both are understood to affect PHP versions 5, 6, 7 and 8.
The scores attached to the vulnerabilities are disputed. The PHP security team assigned each a CVSS v4.0 score of 9.2, while watchTowr and a now-deleted Hacker News post described both as carrying CVSS scores of 10.0. watchTowr also cited an originally planned Thursday disclosure, while PHP scheduled its release for 21 October. The European Union Computer Emergency Response Team said the risk scores indicate the potential for unauthenticated remote code execution.
Where the scores came from
The mechanism is remote code execution: an attacker sends input that the server runs as instructions, which can let them install malware, alter websites or steal data. A researcher estimated that more than 1.3 million internet-connected hosts are likely affected. Wordfence warned that every WordPress site is vulnerable because they run on servers using PHP, and that the fix cannot be installed through automatic updates, so site owners must apply it manually.
Several organisations took websites offline before the patches arrived. The Netherlands' National Institute for Public Health and the Environment removed its website, and the Tweede Kamer, the lower house of the Dutch parliament, became inaccessible. GrapheneOS temporarily took its user discussion forum offline, saying proof of concept exploits were being developed. Pinboard and some parts of Wikipedia were also down as of Wednesday morning.
The UK's National Cyber Security Centre said that where immediate remediation is not feasible, organisations should consider taking the system offline until it can be fully mitigated. CERT-EU recommended isolating internet-facing applications from public networks until a fix is available. Japan's national cyber-security office issued a similar warning, and Japanese websites including daycare centre systems and video game systems went voluntarily offline, the Japanese tech news site ITmedia reported.
Who went offline first
Attackers were already probing targets before the release. Dane Knecht, chief technology officer at internet infrastructure firm Cloudflare, wrote on X that early attacks were emerging and that Cloudflare was updating mitigations as new vectors show up. Patchstack said it had received reports of active exploitation. Sansec threat researchers said they expect to see mass attacks within 15 minutes of the release, while watchTowr said it had not observed exploitation in the wild.
Don Smith, from the Sophos Counter Threat Unit, said the flaws would likely be a priority target for hackers and that the immediate challenge was finding and managing every instance where PHP runs, sometimes without the organisation realising it. He said it was crucial that organisations looked out for signs that an attacker might already have gained a foothold. The NCSC advised continuous monitoring for security updates from third-party vendors after installing the patch.
The PHP security team said it will publish full technical details, affected versions and fixed releases when the security updates become available. Administrators are preparing to install the patches as soon as they arrive, with the release set for 21 October 2026 at 14:00 UTC. The team has not said which specific PHP versions are affected, leaving site owners to identify every server running the language before the updates land.
Frequently asked questions
Which PHP versions are affected?
watchTowr researchers said the flaws affect PHP versions 5, 6, 7 and 8. The PHP security team has not officially disclosed which versions are affected and said full details will come with the patch release.
Why are websites going offline instead of patching?
The UK National Cyber Security Centre and CERT-EU advised taking systems offline if immediate patching is not possible, because the flaws allow unauthenticated remote code execution and the fix cannot be applied through automatic updates.


