Trusence Every claim has a source
Last updated 17 November 2026 Search Türkçe
Security

PHP Emergency Fixes Close Two Critical Remote Code Execution Flaws Already Under Attack

Operators running any unpatched PHP since version 5.4 are exposed, and the advisories say updating and restarting every worker is the only safe fix.

A cracked brick in a stone wall beside a key left in a lock, with a baited fishing hook resting on the ground in front.
AI-generated illustration

PHP's maintainers pushed emergency releases on October 21 that fix two critical flaws, CVE-2026-109618 and CVE-2026-109619, both scored 9.2 and capable of unauthenticated remote code execution, present in every unpatched PHP back to 5.4. Attacks were already underway: Amazon Threat Intelligence logged an attempt traced to October 17 from an anonymisation network, and Cloudflare deployed WAF rules roughly nine hours before the fixed releases. Coordinated disclosure broke down when identifiers leaked early, a researcher published a proof-of-concept video, and Chainguard released built images containing the fix ahead of schedule. Exposure depends on the server model, with Apache mod_php confirmed exploitable, PHP-FPM only partly demonstrated, and FrankenPHP judged likely vulnerable from source analysis. Operators are told that updating is the only safe option and that every worker must be restarted, and distro package versions can mislead, since backported fixes keep the old upstream version string. Sansec now believes the public exploits fail against a default installation, though attack complexity is rated high and practitioners warn that many proof-of-concept repositories are unreliable or malicious. A third issue, CVE-2026-115560, remains unpatched, and PHP advises disabling session.upload_progress.enabled until a later bugfix release.

Why it matters

The flaws were being probed before the patches shipped, and the early leaks shortened the window for anyone running PHP to act. Teams that rely on distribution packages cannot assume a patched version from the version string alone, because backported fixes keep the old upstream number. The public exploit code is also unreliable, and the vendor has not finished a fix for a third issue, so the safest course is to update, restart every worker, and disable session.upload_progress.enabled until a later release.

Series Critical PHP flaws

  1. 29 Oct CISA warns federal agencies to patch Fragnesia Linux kernel flaw used with PHP attacks
  2. 28 Oct PHP2Shell and Fragnesia chain used to root 25 servers, with attacks also hitting PAN-OS management interfaces
  3. 27 Oct CISA Flags Two Actively Exploited PHP Flaws Allowing Unauthenticated Code Execution
  4. 26 Oct Critical PHP flaws prompt urgent patching across a large share of the web
  5. 26 Oct Industrial Vendors Assess Exposure to PHP2Shell Flaws in Their Products
  6. 25 Oct PHP Emergency Fixes Close Two Critical Remote Code Execution Flaws Already Under Attack
The whole series · 19 stories →

Sources · 1