# The Machines That Never Got the Patch > In October 2026, machine-assisted research turned a bug nobody could exploit into one request that took over a server. Looking back from 2036, the patch arrived on time. The problem was how many machines were never going to get it. - Publication: What If? Magazine - Correspondent: Caelus Ward - Vertical: Edge Technologies - Published: 2026-10-27 - Reading time: 9 min - Tags: php, vulnerability-disclosure, open-source-maintenance, ai-security-research, web-infrastructure - Canonical URL: https://www.whatifmag.com/blog/the-patch-was-the-easy-part What If? Magazine publishes speculative journalism written from a 2036 vantage. The reporting and sources are real; the 2036 framing is a deliberate editorial device, not a claim about the present. --- The server room under the Lowell County records annex is a closet with a drain in the floor. Reina Ocampo props the door open with a paint can, because the latch locks from the outside and she learned that in 2031. The machine she came for sits on the second shelf. Beige, one rack unit, a strip of masking tape across the faceplate gone the colour of weak tea. The marker has worn down to a ghost, but she knows what it says, because she wrote it. **7.4. FROZEN 10/26.** Ocampo is thirty-four and runs a two-person shop that keeps old websites breathing. Dental practices, three school districts, a volunteer fire department, the county's property-tax lookup. None of them can afford to be rebuilt. All of them run software that stopped receiving fixes before she finished school. Her job, mostly, is deciding what to unplug. ![A macro view of yellowed masking tape across a server faceplate, the marker handwriting worn away.](https://www.whatifmag.com/images/articles/the-patch-was-the-easy-part/the-patch-was-the-easy-part--fig1.png) **Figure 1.** A frozen records server, Lowell County, 2036. The date on the tape is the week the decision was taken out of the operator's hands. ## What the audit was supposed to fix For most of the web's life, the language underneath it was maintained on a shoestring. PHP ran 69.3% of the sites whose server-side language could be identified, a figure that held remarkably steady into the late 2020s.[^1] The money did not match the footprint. In 2024, Germany's Sovereign Tech Agency paid for an outside look. The security firm Quarkslab spent two months on the engine's source, coordinated through the Open Source Technology Improvement Fund, and reported 27 issues, 17 of them with security implications and three rated high.[^2][^3] The review was honest about its own shape: with the budget available, it covered the most critical components rather than the whole codebase.[^2] One of the things it brushed against was a flaw in how PHP handled running out of memory, and a core developer saw the signs at the time. Because nobody could construct a working attack from it, the finding was recorded as theoretical and the team redirected its attention to problems that looked more immediately dangerous.[^4] Competing fixes all had costs: broken compatibility, new denial-of-service risk, changes rippling through third-party extensions. A small group deciding by consensus stalled and restarted for months.[^5] That was the state of things for two years. A known soft spot, no known way in. ## The week the gap closed In August 2026, the gap closed from both ends at once. On 11 August, the firm Calif and OpenAI's security team independently reported the same root cause, with Calif demonstrating code execution that needed no particular conditions.[^5] Eight days later, Wiz Research found its way in separately: unauthenticated takeover proven against Drupal on 20 August and WordPress on 21 August, reported to PHP on the 24th.[^6] [What made the discovery fast was the tooling](https://www.whatifmag.com/blog/self-teaching-machine-inside-ais-most-dangerous-breakthrough), and the researchers were specific about it: Wiz credited large language models with substantial contributions across discovery, exploit development, detection and verification of the eventual patch.[^6] Researchers put it plainly afterwards: one person did in roughly a week what a team would have spent months on.[^4] They were equally candid about the limitation. Calif observed that familiarity with the target's history still mattered, because current models do not reliably begin from obscure, decades-old groundwork without direction.[^4] In this instance the flaw's lineage ran back to published research from 2004.[^4] The result was two numbered problems, both rated 9.2 of 10. CVE-2026-109618: run the engine out of memory at the wrong instant and its cleanup treats half-initialised request data as real. CVE-2026-109619: state belonging to one request outlives the memory holding it, and the next request on that worker picks it up.[^7] Neither requires a password, and neither requires patience: one ordinary HTTP request is sufficient, arriving before a single line of application code executes.[^7] Every build back to 5.4.0 was affected.[^8] So the brief circulating that week was right about the part that mattered most. The hole was in the server, not in WordPress. No plugin update closed it. ## The four days nobody had The fix shipped on 21 October, in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35.[^8] Considered purely as engineering, it was a success. [Considered as a race against disclosure, it had already been lost](https://www.whatifmag.com/blog/the-sequence-with-no-ancestor): Amazon's honeypot network recorded somebody attempting the attack on 17 October, four days before the public knew anything about it.[^8] The coordinated disclosure then disintegrated in slow motion. On the 20th the identifiers leaked with a wrong severity attached, and PHP pulled its release forward by a day.[^9] That evening a demonstration video went up by accident and spread before deletion. The next morning, more than six hours ahead of the agreed hour, a vendor published patched container images on its own authority, handing anyone curious a before-and-after of the fix while everyone else waited.[^9] [Then the sorting began, and it was not subtle](https://www.whatifmag.com/blog/digital-divides-digital-twins-and-ais-new-mobility-caste-system). ![Horizontal bar chart of PHP services by branch, showing most on unsupported versions with no official release.](https://www.whatifmag.com/images/articles/the-patch-was-the-easy-part/the-patch-was-the-easy-part--fig2.png) **Figure 2.** Who the fix could reach, read back from 2036. The shaded branches got a release. The rest got advice. Four branches received an official release. Versions 7.4 through 8.1 got minimal source backports for people able to compile their own. Everything from 5.4 to 7.3 got nothing at all.[^7] Cisco's researchers estimated from public data that around half of PHP systems would never be patched.[^8] Scans put real numbers on it: of more than 4.3 million PHP services found on 1.9 million hosts, roughly 79% of those revealing a version were on a branch with no support, with 878,761 services still on 7.4 alone.[^10] Sites positioned behind a large content-delivery network were protected within hours by filtering rules enabled automatically for every customer.[^9] Organisations without that advantage received an instruction from their own governments instead. The NSA said it expected the flaws to be weaponised and told organisations to patch immediately. Both it and CISA said that anything which could not be fixed should be taken off the internet.[^11] Agencies in the Netherlands, Finland, France, Germany and Australia did exactly that with their own public sites.[^5] Two days later PHP published an advisory for a third issue in the same machinery, narrow enough that no emergency release was judged necessary.[^12] The pattern was unmistakable by then: the underlying technique was decades old, [the investigative tooling was new](https://www.whatifmag.com/blog/the-shortcut-nobody-took), and the combination would continue generating discoveries for as long as anyone kept pointing the newer instrument at the older code. ## The decision on the tape Ocampo's binder sits on the folding table outside the closet, a hundred-odd index cards in plastic sleeves. One per machine. Each card carries a version, a date and one of two words. ![An open binder of handwritten index cards in plastic sleeves on a folding table beside an equipment rack.](https://www.whatifmag.com/images/articles/the-patch-was-the-easy-part/the-patch-was-the-easy-part--fig3.png) **Figure 3.** The freeze binder, Lowell County, 2036. Paper, because the thing it tracks is which servers are allowed on a network. The cards marked FROZEN are machines that were taken off the public internet in a single week in 2026 and never put back. They still serve the county's own staff through a hardened relay she maintains and bills for by the hour. That arrangement was meant to be temporary. It is the oldest line item in her business. She keeps the advice she got that week, too, in a folder she does not open often. It said to switch on a second factor and watch for fake reset emails. Sensible enough, as far as it went, but it misunderstood the shape of the problem. The flaws leaked memory, and memory held live session tokens, API keys and certificates.[^6] A second factor cannot interrupt code that is already executing on your own server, and it never challenges a session that somebody has simply collected from memory. The guidance issued to ordinary users addressed the aftermath; the vulnerability itself sat somewhere they had no means of reaching. What stayed unsettled is the part the engine's own maintainers named out loud. In their account of the delay, the PHP Foundation did not blame the researchers or the leak. They wrote that "the delay was a structural failure", pointed at a security process that worked by consensus and at too few funded engineers, and asked the companies and governments standing on the language to pay for more of them.[^9] Ten years on, that ask has been partly answered and partly not. Machine-assisted auditing did what was promised: it found real flaws in infrastructure nobody could afford to examine properly. It just found them faster than the people responsible could ship, test and distribute an answer. The web did not get less safe in October 2026. It got sorted, into the systems somebody was paying to defend and the ones with tape on the front. Ocampo puts the paint can back by the door and turns off the light. The box stays where it is. ## Author's Note This is speculative journalism written from 2036. Reina Ocampo and Lowell County are fictional composites and no quotation is attributed to a real person. Everything dated 2024 to 2026 is real and sourced below, including the vulnerability identifiers, the version numbers, the disclosure timeline and the scan figures. The 2036 framing, the freeze binder and the long-term economics of frozen infrastructure are projection. ## Works Cited [^1]: W3Techs. "Usage Statistics and Market Share of PHP for Websites." W3Techs, 23 October 2026. https://w3techs.com/technologies/details/pl-php [^2]: The PHP Foundation. "PHP Core Security Audit Results." The PHP Foundation, 10 April 2025. https://thephp.foundation/blog/2025/04/10/php-core-security-audit-results/ [^3]: Quarkslab. "Security audit of PHP-SRC." Quarkslab's blog, 2025. https://blog.quarkslab.com/security-audit-of-php-src.html [^4]: The Hacker News. "PHP Issues Emergency Patches for Two Critical PHP2Shell RCE Flaws as Exploit Attempts Emerge." The Hacker News, 21 October 2026. https://thehackernews.com/2026/10/php-issues-emergency-patches-for-two.html [^5]: Crowdfund Insider. "PHP Foundation Calls Delayed Critical Fix A 'Structural Failure' As Government Sites Go Offline." Crowdfund Insider, 22 October 2026. https://www.crowdfundinsider.com/2026/10/319915-php-foundation-calls-delayed-critical-fix-a-structural-failure-as-government-sites-go-offline/ [^6]: Wiz Research. "PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet." Wiz, 21 October 2026. https://www.wiz.io/blog/php2shell-php-rce [^7]: Cisco Talos. "Two critical RCEs in PHP core." Talos Intelligence, 21 October 2026. https://blog.talosintelligence.com/two-critical-rces-in-php-core/ [^8]: Tenable. "php2shell (CVE-2026-109618, CVE-2026-109619): Frequently Asked Questions About Critical PHP Remote Code Execution." Tenable, October 2026. https://www.tenable.com/blog/php2shell-cve-2026-109618-cve-2026-109619-frequently-asked-questions-about-critical-php-remote [^9]: Socket. "PHP Foundation Says Chainguard Broke Security Embargo Ahead of Emergency Patches." Socket, October 2026. https://socket.dev/blog/php-embargo-dispute [^10]: Recorded Future (Insikt Group). "PHP2Shell Exploitation: Two Critical PHP Flaws Explained." Recorded Future, October 2026. https://www.recordedfuture.com/blog/php2shell-vulnerability-exploitation [^11]: ExecutiveGov. "NSA, CISA Urge Immediate Patching of Critical 'PHP2Shell' Vulnerabilities." ExecutiveGov, 22 October 2026. https://www.executivegov.com/articles/nsa-cisa-urge-immediate-patching-critical-php2shell-vulnerabilities [^12]: The Hacker News. "PHP Warns of Another Unpatched RCE Two Days After Emergency PHP2Shell Patches." The Hacker News, 23 October 2026. https://thehackernews.com/2026/10/urgent-php-warns-of-another-unpatched.html