<figure class="news-cover"><img src="https://aposhuang.com/uploads/covers/news-165-030f34bd.jpg" alt="" loading="eager"></figure>
<p>The PHP security team released emergency patches on October 21 for two critical vulnerabilities that allow unauthenticated attackers to run code on servers running the language that powers most of the public web. The flaws are tracked as CVE-2026-109618 and CVE-2026-109619, and collectively as PHP2Shell. They were found by researchers at Calif, OpenAI and Wiz.</p>
<h2>What happened</h2>
<p>The patches affect every PHP installation that serves web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. Admins running PHP 8.x should install 8.5.12, 8.4.27, 8.3.36 or 8.2.35; anyone still on PHP 7 or earlier is being told to migrate to a fixed release.</p>
<p>Both bugs come from the same root cause. When a request ends abnormally, PHP can leave its memory in a corrupted state, and that corrupted state can be turned into remote code execution. CVE-2026-109618 chains a set of weaknesses around out-of-memory handling to run code as the web worker account. CVE-2026-109619 is a stale global state flaw that enables unauthenticated heap use-after-free, memory disclosure and code execution with the worker's privileges.</p>
<p>"We consider the risk highest for mod_php, with a demonstrated exploit where an unauthenticated request can trigger the attack before any application code runs," the PHP security team said. That detail matters: a vulnerable mod_php host can be compromised by a single crafted request, with no plugin, theme or application route involved.</p>
<p>PHP 8.1 and older no longer receive updates from the project. The team said some distributions and long-term-support vendors provide backported fixes, and that it had prepared minimal source backports for PHP 7.4, 8.0 and 8.1 for people who build from source or have no LTS vendor.</p>
<h2>Why it matters</h2>
<p>The disclosure is a milestone less for the bug class than for how it was found. A pair of memory-safety flaws in a runtime this old, this widely deployed and this heavily audited would normally surface through years of manual review, if at all. Here, three organizations working with machine-assisted analysis converged on the same two defects in the same request-handling path. Whatever else is true, the economics of finding deep bugs in mature infrastructure code have changed.</p>
<p>The second reason is exposure. PHP runs somewhere between 75% and 80% of all websites, including sites built on WordPress, Joomla and Drupal. VirusTotal estimates put more than 5.1 million PHP hosts online, roughly 3.8 million of which have at least one port open. A pre-authentication bug in the runtime sits underneath every one of those sites, regardless of how carefully the site itself was written.</p>
<p>The third is that patching is the only real fix. Gina Peter Banyard, a PHP core developer, warned that no PHP2Shell mitigation fully blocks potential attacks and that applying the official security updates is the only permanent defense. Cloudflare had already deployed WAF rules for known exploitation methods, and its CTO Dane Knecht confirmed the company was observing early attacks before the patches landed, while stressing that those protections were temporary. The UK's National Cyber Security Centre told organizations to update immediately or take systems offline until they could be patched.</p>
<p>It is worth being precise about what this is not. There is no evidence here of a worm, and no indication that every PHP host is compromised. The honest reading is narrower and more uncomfortable: an internet-facing runtime flaw that needs no credentials, no user interaction and no application bug is the kind of thing that gets exploited quietly, at scale, and shows up months later in logs nobody kept.</p>
<h2>What it means for Europe and the US</h2>
<p>For hosting providers, agencies and anyone running a long-lived WordPress estate, the practical problem is inventory. Shared hosts often run one PHP version for thousands of tenants and cannot restart cleanly without coordination. Container images built months ago carry the old runtime until someone rebuilds them. The version string in a header or a phpinfo page is not proof of the patched binary; only the package version and a restart are.</p>
<p>Regulators will read this through the lens of duty of care. The UK NCSC's instruction to patch or go offline is a strong signal, and in the EU the combination of the Cyber Resilience Act's product-security expectations and NIS2 incident reporting makes an unpatched, internet-facing runtime harder to defend after the fact. For small businesses the realistic answer is not a security team but a hosting contract that states who patches and how fast.</p>
<h2>What to watch</h2>
<p>Whether public exploitation shifts from opportunistic scanning to mass automated attacks within the next two weeks.</p>
<p>How many hosts remain on PHP 8.1 or earlier, which now have no upstream fixes at all.</p>
<p>Whether shared-hosting providers publish per-tenant patch status, or leave customers to guess.</p>
<p>Whether other runtimes disclose similar memory-corruption findings that were located with the same machine-assisted methods.</p>
<p class="src">Source: <a href="https://www.bleepingcomputer.com/news/security/php-ships-emergency-patches-for-critical-php2shell-flaws/">BleepingComputer, October 21, 2026</a></p>
<aside class="tl-cta" style="margin:28px 0;padding:18px 20px;border-left:3px solid #38bdf8;background:#0d1526;border-radius:8px"><p style="margin:0 0 6px"><strong>在日の手続き・住まい・引っ越しの相談先</strong></p><p style="margin:0;color:#93a3c4">言語別に相談できる事業者をまとめています。<a href="/services" style="color:#38bdf8">相談先を見る →</a></p></aside>