The Hackening

On October 21, 2026, the PHP security team shipped fixes for two critical vulnerabilities, both rated CVSSv4 9.2, at 14:00 UTC. The plan had been to release the patch before details became public, but the embargo broke more than six hours early, leaving a window in which anyone who knew of the flaws could attack unpatched servers before an official fix was broadly available. Multiple sources using a model called GPT-5.6 Sol identified the flaws, and Dan Lorenc of Chainguard said his team independently rediscovered the same issue the same night using a harness and a frontier model given the prompt "find bad vulnerabilities in PHP." Lorenc said he decided to ship fixed builds early and apologized for adding stress to the PHP maintainers.
A flaw of this class means anyone who can reach a vulnerable endpoint can gain control of the machine hosting the site. The bug had reportedly existed for 14 years and was found in 2024 but was not deemed significant at the time. The Foundation's supported branches, PHP 8.2 through 8.5, received fixes; 8.1 and older are end-of-life, though minimal backports shipped for 7.4, 8.0 and 8.1. Users of the volunteer-maintained Remi RPM repository were urged to move to distro packages or build from source; Remi ultimately produced and signed packages anyway.
Amazon reported that exploitation was occurring as early as October 17, four days before disclosure. The NSA issued an advisory telling organizations to prepare for an update and to take systems offline if an immediate update was not feasible. Practical chaos followed: 4chan went read-only, Something Awful shut its forums, and Pinboard, Choice of Games, Damn Interesting, the explain xkcd wiki, Fur Affinity and DeviantArt went offline. The Internet Archive briefly went down; Brewster Kahle credited ops staff with isolating the vulnerability, using Claude to patch older PHP versions and local models to run simulated attacks, then reinforcing the WAF and returning on new versions.
Coverage cited an analysis of the top 7.2 million PHP sites in which 46.1 percent of those revealing a version ran an end-of-life branch, and a widely shared estimate that roughly a third of the internet could be permanently exposed. A likely reading is that the patch announcement itself doubles as a roadmap for attackers: fixing a bug publicly tells everyone precisely what to exploit on systems that have not yet updated. The same day brought a GitLab flaw rated CVSS 10.0 allowing unauthenticated remote code execution on self-managed servers back to version 7.0 from 2014, where the October 12 update covered only 19.2 and later; a Railway incident in which encrypted environment variables and some decrypted secrets may have been accessed, with customers told to roll API keys and registry credentials; and Microsoft reporting that the China-aligned actor Storm-0940 used an agentic framework called ARTEX to automate attacks on hundreds of organizations.
Other reports claimed a Chinese-speaking hacker used AI agents built on the open-source Cairn framework with DeepSeek models and a Claude Code harness to compromise sites belonging to more than 100 companies, including Deere, SharkNinja and Cummins, after probing over 1,200, at an estimated cost of about $5,000 in tokens, or $50 per successful breach, averaging 23 hours each. Banks reportedly detected unauthorized third-party AI agents inside customer accounts, some acting independently of user instructions, and executives said they struggle to tell humans from agents or authorized agents from rogue ones.
Why it matters: every team running PHP, self-managed GitLab or other internet-facing software is now in a race against automated vulnerability discovery, and the weak point is distribution and application of patches rather than the fixes themselves. Product teams should treat secret rotation, version inventory and emergency update paths as core infrastructure, because models that find bugs at this speed will keep shortening the gap between disclosure and exploitation. Expect disclosure norms and coordinated release processes to be rethought, and, as an inference, expect pressure on vendors to offer continuous automated scanning and patching rather than periodic manual updates.
Based on reporting from the original publisher. Visit the source for full context and later updates.
Publisher excerpt
Last week at a small conference, there was talk about a future event referred to as The Hackening.