{"id":9119,"date":"2026-10-22T02:52:40","date_gmt":"2026-10-22T02:52:40","guid":{"rendered":"https:\/\/silvybrand.com\/?p=9119"},"modified":"2026-10-22T02:52:40","modified_gmt":"2026-10-22T02:52:40","slug":"php2shell-vulnerability-october-2026","status":"publish","type":"post","link":"https:\/\/silvybrand.com\/?p=9119","title":{"rendered":"Here\u2019s why Wikipedia and a lot of the internet shut down today"},"content":{"rendered":"


\n<\/p>\n

\n
\n

Two bugs found with AI are behind major issues today for 4chan, DeviantArt, Wikipedia<\/a>, and the blog where the bar around the corner posts pictures of people\u2019s dogs. The \u201ccritical vulnerabilities\u201d were discovered in the PHP programming language, which underpins much of the internet, including any site built on WordPress. But it\u2019s far bigger than that. Some Dutch and Finnish government agencies took their sites down as a precaution. The NSA Cybersecurity account on X recommended that<\/a> organizations take their systems offline if \u201can immediate update is not feasible,\u201d as did the UK\u2019s National Cyber Security Center<\/a>. Even Pok\u00e9mon Home<\/em> and Pok\u00e9mon Champions<\/em> were taken offline, Kotaku<\/em> reports<\/a>.<\/p>\n<\/div>\n

\n

The vulnerability isn\u2019t exactly new. It\u2019s been present in PHP for roughly 20 years, but exploiting it \u201crequired an exceptionally complex chain of steps, at the edge of what human researchers could practically achieve,\u201d according to security firm Wiz<\/a>. However, powerful AI models have made it much easier to turn that kind of obscure bug into dangerous vulnerabilities.<\/p>\n<\/div>\n

\n

As a casual internet user, you might be wondering what exactly the barrage of jargon like \u201cRCE via OOM corruption\u201d means, how concerned you should be, and how exactly a vulnerability this severe flew under the radar for so long.<\/p>\n<\/div>\n

\n

W3Techs, a survey service, says that<\/a> the PHP programming language is used by \u201c69.3 percent of all the websites whose server-side programming language we know,\u201d including popular sites like Wikipedia and WordPress. The internet security site VirusTotal says its scanner<\/a> currently registers about 3.8 million sites running PHP with at least one port open.<\/p>\n<\/div>\n

\n

According to OpenAI<\/a>, an AI security group called Calif<\/a> identified a \u201ccritical\u201d PHP flaw using GPT-5.6 Sol, and Google-owned Wiz independently discovered and reported<\/a> the vulnerabilities using AI. The PHP Foundation says that an exploit for one of the vulnerabilities \u201cwas theorized\u201d in 2024, but \u201cno concrete vectors were found and other concrete issues with clear impact overshadowed these concerns.\u201d<\/p>\n<\/div>\n

\n

Now the PHP Group says hackers could use the two vulnerabilities for \u201cunauthenticated remote code execution,\u201d like running their own code, changing content, and accessing a site\u2019s stored data without needing an administrator login or password.<\/p>\n<\/div>\n

\n
\n

RCE via OOM corruption, CVE-2026-109618 (GHSA-w8hw-w9fx-j79w<\/a>): out-of-memory handling can interrupt PHP while internal request data is only partially initialized. Request cleanup may then treat the invalid data as valid.<\/p>\n

RCE via stale global state, CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp<\/a>): request-owned internal state can survive after its backing memory has been freed. A later request handled by the same worker may use that stale state before normal initialization resets it.<\/p>\n<\/blockquote>\n<\/div>\n

\n

Very. The PHP Group says that basically any site running PHP is at risk. OpenAI, which was involved in the vulnerability research, said: \u201cWe consider this one of the most impactful security issues in recent memory.\u201d And Wiz said it\u2019s \u201camong the most severe vulnerabilities discovered \u2026 in software history.\u201d<\/p>\n<\/div>\n

\n

Last night, the CTO of Cloudflare said that<\/a> it was \u201cseeing early attacks emerging.\u201d<\/p>\n<\/div>\n

\n

It\u2019s hard to understate just how bad this could get. The vulnerabilities could allow an attacker to take full control of a server. That includes gaining access to passwords, API keys, cryptographic certificates, and databases of sensitive information. They could also execute code on those servers, turning them into vectors to attack other vulnerable servers. And, thanks to AI, it\u2019s relatively trivial for a determined hacker to exploit these flaws now that they have been revealed.<\/p>\n<\/div>\n

\n

As a user, not much. The vulnerability affects servers running PHP and doesn\u2019t necessarily target users directly, but it could use compromised sites to spread malware and steal other valuable data. If you\u2019re feeling extra cautious, check the social accounts of sites and services you frequently use to see if they\u2019ve posted any updates before visiting.<\/p>\n<\/div>\n

\n

If you have a website, even a simple blog, it\u2019s time to check what version of PHP your site uses, if any. If you\u2019re using a service like Squarespace or Wix, you\u2019re in the clear, as those don\u2019t support PHP.<\/p>\n<\/div>\n

\n

Customers of Hostinger, GoDaddy, Bluehost, or other web hosting services should be more cautious. GoDaddy<\/a> says that any site using PHP should assume it is affected and update to the fixed release as soon as possible. It also says that sites running PHP 8.1 or older should upgrade to a newer version, as they\u2019re no longer supported and there will not be an official fix coming.<\/p>\n<\/div>\n

\n

Those on a managed hosting service should check with their provider to see when they should expect the fix to be deployed. If you sell products or services or have any sensitive data on your servers at all, it\u2019s best to disable your site until your host patches their version of PHP.<\/p>\n<\/div>\n

Follow topics and authors<\/strong> from this story to see more like this in your personalized homepage feed and to receive email updates.<\/span><\/p>\n