Lead · Vulnerabilities
PHP patched the internet's plumbing at two in the afternoon; the sensors had company before lunch
Two critical unauthenticated RCE flaws in PHP itself, an out-of-cycle release at 14:00 UTC, and a workaround that the firm which suggested it has now said is not enough on its own.
The PHP security team shipped emergency fixes for CVE-2026-109618 and CVE-2026-109619, known collectively as PHP2Shell, in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and said plainly that only updating fully protects a server. Before the release landed, several security companies reported exploitation attempts against both CVEs. SANS raised infocon to yellow on the strength of widespread use, the expected severity and the availability of early PoC exploits ahead of the patch. The feeds cannot agree on whether this is a 9.2 or a 9.4, which tells you roughly everything about how much CVSS is doing for you this morning.
The scale is in the plumbing rather than the product. Nearly seventy percent of websites need to update their core software to fix the pair, with hundreds already taken offline as the concern spread, and the one configuration setting being passed around as mitigation was publicly downgraded by the firm that proposed it. The PHP Foundation's own account is the uncomfortable part: one of the flaws dates to 2024, a third-party review by AI companies heightened attention in August, and the team then scrambled to publish earlier than planned. The code was wrong for two years. The alarm went off in August. The fix went out on a Wednesday afternoon with exploit attempts already in flight.
This is not a story about PHP being bad. It is a story about where the control actually lives, which is in a version number and not in a directive, a WAF rule or a sentence in a status page. Everything between knowing and patching is weather. You cannot post a workaround into being sufficient.
Why it mattersIf you run PHP anywhere, including that one marketing box nobody owns, the only non-incident state today is a patched version; treat the config workaround as a delay, not a defence.
- 1RSSPHP ships emergency patches for critical PHP2Shell…
- 2Security newsPHP ships emergency patches for critical PHP2Shell…
- 3Security newsPHP2Shell: Two Unpatched Critical PHP RCE Flaws (CV…
- 4Security newsPHP2Shell Patches Land as First Exploitation Attemp…
- 5Security newsPHP Issues Emergency Patches for Two Critical PHP2S…
- 6Security newsWidespread PHP Flaw May Cause Many Site Outages Tod…