← Back to Tech · Phones & Mobile
a vast dark server hall with rows of glowing server racks, one aisle flooded with warning red light while engineers in silhouette rush toward it, a translucent shield of blue light spreading rack by rack behind them, no logos, no text

PHP2Shell: emergency patches land for critical PHP flaws that could let attackers take over websites

This is the big one today. The PHP team shipped emergency updates on Wednesday, Oct 21 for two critical flaws, nicknamed PHP2Shell, that can let an attacker run code on a web server without logging in. PHP powers WordPress, Drupal, Joomla and Wikipedia’s MediaWiki, and the PHP team says “all PHP users are strongly encouraged to update immediately” (PHP.net).

What happened

  • Two CVEs, both rated 9.2. CVE-2026-109618 and CVE-2026-109619 come from how PHP cleans up after a request crashes, especially when it runs out of memory. Leftover data can be reused by the next request.
  • Who’s at risk: any PHP install that serves web pages, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. PHP rates mod_php as the highest risk.
  • Old bugs, found with AI. Wiz Research says the flaws reach back to PHP 5.4 and that frontier AI models made a working exploit practical. Wiz and Calif found them with help from Google and OpenAI models (Wiz).
  • Attacks have started. Cloudflare says it saw attack traffic after details leaked early and has blocked known exploit patterns for WAF customers since 3:02 a.m. UTC Oct 21 (Cloudflare). watchTowr told Cybersecurity Dive no attempt had succeeded yet, but it doesn’t expect that to last.

Sites going dark

CISA, the NSA and agencies in the U.K., Canada, Australia, the EU and Japan urged anyone who can’t patch to take sites offline. Finland paused government web services, some Dutch government sites went down, and Wikimedia pulled some systems as a precaution (BBC, Cybersecurity Dive).

What to do

  • Update PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35. Linux distributions got the fixes early, so check your package updates.
  • On PHP 8.1 or older? Those versions are out of support. PHP’s security team posted minimal source backports for 7.4, 8.0 and 8.1 for people who build PHP themselves, but the safer move is to upgrade or ask your host or LTS vendor for a patched package.
  • Use a host? Check that your web host or WordPress provider has patched. Config tweaks only narrow the risk; PHP says updating is the only real fix.

How many sites are exposed isn’t settled. Wiz says PHP runs about 70% of websites, but estimates of actually vulnerable servers range from about 1.3 million to more than 22 million.

Update, Oct 21 afternoon: CISA weighs in

CISA posted an alert urging organizations to patch immediately, inventory everywhere PHP runs (it’s often bundled inside other software) and take PHP systems offline if they can’t update or are still on PHP 8.1 or older. CISA says it had not observed exploitation when it published (CISA).

Security firms tell a busier story. Patchstack, Cloudflare and Vega reported exploitation attempts, and watchTowr says none it saw had succeeded yet. One firm, Hadrian, says it’s seeing attacks “at scale,” a claim others haven’t confirmed (SecurityWeek). The PHP team also posted minimal source backports for PHP 7.4, 8.0 and 8.1, a rare step for versions it no longer supports (PHP.net).

Update, Oct 22 morning: attacks started before the patch

Amazon’s threat intelligence team says one of its honeypots caught a PHP2Shell exploit attempt on Oct 17, four days before the fix was public, from an anonymizing network. It’s not clear how the attacker got the details early, and Amazon says it’s unclear whether those early attempts would have worked on real systems. Its advice: if you run PHP, investigate back to at least Oct 17, not just from the day of the patch (AWS Security Blog).

The flood is on now. Amazon says PHP2Shell is “now being broadly exploited in the wild.” Cloudflare’s CEO says attempts on its network went from thousands before the announcement to millions by Thursday morning, while watchTowr says the exploits it’s seeing mostly don’t work or just crash the target. Censys counted roughly 1.57 million internet-facing hosts still unpatched on Oct 21 (SecurityWeek).

Update, Oct 23 midday: lots of attempts, no confirmed break-ins

Two days after the patch, attackers have tried to use PHP2Shell to spread Potassium, which Sophos believes is a variant of the Mirai botnet. The attempt Sophos analyzed was blocked, and it corrected an earlier update that had reported a successful exploitation. Hunt.io and Wordfence also see attacks continuing, but no one has confirmed a successful in-the-wild compromise so far (SecurityWeek).

Attackers seem to be struggling. Sansec now says success takes detailed knowledge of a server and particular conditions, and that public exploits fail against default PHP setups. The warning sign: VulnCheck built an exploit for CVE-2026-109618 that gets past ASLR on production-style settings (it’s for paying customers only). Qualys estimates about 71% of PHP instances it sees run end-of-life versions 5.4 through 8.1, and as of Friday morning CISA had not added the flaws to its Known Exploited Vulnerabilities catalog (SecurityWeek).

Update, Oct 26 morning: first confirmed successful attack

The “no confirmed break-ins” line no longer holds. Perplexity detection lead Adel Karimi says his honeypots recorded a confirmed remote code execution against an Apache mod_php server running PHP 8.4.26, an unpatched version. Expel researcher Marcus Hutchins called it “by far the highest quality confirmation of in-the-wild php2shell exploitation I’ve seen so far” (BleepingComputer).

One more thing to know: on Friday the PHP team published mitigations for a separate, unpatched RCE bug, CVE-2026-115560. It only works on servers with an “unusual combination of configuration and application code.” Until a fix ships, PHP advises setting session.upload_progress.enabled=0. The fixed PHP2Shell releases are still 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

Koffee take: this is a patch-tonight story for anyone running a website, and a sign of how fast AI is speeding up both the bug hunt and the attacks. If you run a WordPress blog or a small business site, check with your host today. (The Koffee Table is a static site and doesn’t run PHP.)

Filed Oct 21, 2026 ~12:30 PM CT — Midday pass. Updated Oct 21, 2026 ~4:45 PM CT — Afternoon pass. Updated Oct 22, 2026 ~9 AM CT — Morning pass. Updated Oct 23, 2026 ~12:30 PM CT — Midday pass. Updated Oct 26, 2026 ~9 AM CT — Morning pass. Sources: BleepingComputer — PHP2Shell security flaws now successfully exploited in the wild (Oct 26, 2026) · CISA — Critical Vulnerabilities in PHP Require Immediate Patching (Oct 21, 2026) · SecurityWeek (Oct 21, 2026) · PHP.net — Security advisory and PHP 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35 releases (Oct 21, 2026) · Wiz Research — PHP2Shell (Oct 21, 2026) · Cloudflare Blog (Oct 21, 2026) · BBC News (Oct 21, 2026) · Cybersecurity Dive (Oct 21, 2026) · BleepingComputer (Oct 21, 2026). · AWS Security Blog — Amazon Threat Intelligence (Oct 21, 2026) · SecurityWeek — Exploitation started days before patches (Oct 22, 2026) · SecurityWeek — Mirai botnet operators join PHP2Shell attacks as ASLR bypass exploits emerge (Oct 23, 2026). Exposure estimates vary widely by source.