PHP2Shell: The Critical PHP Vulnerability You Need to Patch Right Now (CVE-2026-109618)

What Is the PHP2Shell Vulnerability?

If your website runs on shared hosting, there is a good chance it runs on PHP – and right now, PHP has a serious problem. Security researchers have confirmed two critical remote code execution (RCE) vulnerabilities in PHP core, tracked as CVE-2026-109618 and CVE-2026-109619. The PHP security team rates both at CVSS v4.0 9.2, which is firmly in critical territory, and CERT-EU notes that score points to possible unauthenticated RCE – meaning an attacker may not even need a login to exploit it.

Researchers have nicknamed the pair “PHP2Shell”, and the name tells you everything about the impact: a successful exploit hands the attacker a shell on the server. This isn’t a bug in one app or plugin. It’s in the PHP interpreter itself, so every site running a vulnerable PHP version is exposed, regardless of what CMS it uses. WordPress, Drupal, and most shared hosting stacks sit right in the blast radius.

According to the UK’s National Cyber Security Centre, CVE-2026-109618 allows RCE through RFC 1867 input parsing out-of-memory corruption, while CVE-2026-109619 allows RCE through global state corruption after a fatal error. I’ve followed a lot of vulnerability disclosures over the years, and the thing that separates the scary ones from the routine ones is how fast they move from theory to working exploit – and this one is moving very fast.

How PHP2Shell Blew Up: The Leak

Here’s the part that made this go from “patch Tuesday” to headline news. On October 20, 2026, details of the two flaws leaked publicly ahead of a coordinated disclosure, shattering the embargo that was supposed to give hosting providers and Linux distributions time to ship patched builds. The original coordinated disclosure was set for October 22, but after the leak the PHP security team pushed the patch release up to October 21, 2026 at 14:00 UTC – and warned it could ship even earlier if technical details spread further or real exploitation showed up.

Security firm watchTowr confirmed the vulnerabilities are real and says it successfully reproduced CVE-2026-109618. No public proof-of-concept exists yet, which is the only reason this hasn’t turned into a full-blown mass-exploitation event already. In my experience, that quiet period never lasts long once a vulnerability this severe leaks.

Why Everyone Is Taking This So Seriously

You can usually judge how bad a vulnerability is by who panics first. With PHP2Shell, entire organizations started pulling their own sites offline before any patch existed:

  • In the Netherlands, services including DigiD, MijnOverheid, the Dutch House of Representatives website, tech news site Tweakers, and even the Dutch National Cyber Security Centre’s own site went offline as a precaution.
  • In Japan, emergency maintenance hit major services including Kodmon, Shadowverse: Worlds Beyond, and Sakura Rental Server.
  • The developers of The SEO Framework, a widely used WordPress plugin, took their own servers offline.

Meanwhile Cloudflare rolled out an initial set of WAF rules covering the known exploit vectors for all customers, including free-tier ones – and Cloudflare’s CTO says the company is already seeing early attacks emerging, with mitigations being updated as new attack vectors show up. That is about as clear a signal as you get that attackers are probing this in the wild right now.

Which PHP Versions Are Affected (and Which Get a Fix)

PHP has not published a final affected-version list yet, but public reporting indicates every release from PHP 5 onward is affected. Upstream fixes, however, are only coming to the currently supported branches. Here’s where things stand:

PHP versionStatus
PHP 8.2, 8.3, 8.4, 8.5Fix expected: 8.2.35, 8.3.36, 8.4.27, 8.5.12 (pre-release reports)
PHP 8.0 (EOL November 2023) and 8.1 (EOL December 2025)Not supported upstream – don’t count on a fix
PHP 5 and PHP 7 (end of life)No fix expected – migrate to a supported PHP 8 branch

This is the uncomfortable part of the story. A large share of internet-facing servers still run PHP 5 or 7, and those branches are not expected to receive fixes at all. If that’s you, patching is not an option – only migration, isolation, or a WAF stopgap will help.

How to Check Your PHP Version and Patch It

First, figure out what you’re actually running. On a VPS or dedicated server, php -v gets you started – but note the version reported by the CLI binary isn’t always the one serving your web traffic, so confirm with your hosting panel too. In WordPress, go to Tools > Site Health > Info > Server and you’ll see the PHP version right there. Most shared hosts have a “Select PHP Version” or similar option in cPanel.

Then the fix itself: update PHP the moment the fixed build is available. On shared hosting, your provider usually rolls these out for you – but don’t assume. Open a ticket or check their status page, because this is not one of those patches you can sit on for a month. One PHP core developer put it bluntly: patching or upgrading PHP is the only real mitigation.

Microsoft’s November Patch Tuesday landed the same week, fixing 1,094 flaws including an exploited Outlook bug and a zero-click Windows Search flaw.

And this is important: updating your WordPress plugins, your theme, or your CMS does nothing here. The flaw is in PHP itself. I’ve seen too many site owners “patch” the wrong layer in moments like this and assume they’re safe. Don’t be that person.

Still on PHP 5 or 7? The Clock Already Ran Out

If your server runs PHP 5 or 7, I’ve got bad news: there is no patch coming for you. Those branches are end of life, and the PHP team won’t be shipping fixes for them. Your options are migrating to a supported PHP 8 branch, isolating the server so it’s not internet-facing, or leaning on a WAF as a temporary stopgap while you migrate. Honestly, if you’re still on PHP 5 in 2026, PHP2Shell is just the latest reason to move – the unsupported-version list gets longer and scarier every year.

What Cloudflare and WAF Rules Actually Do (and Don’t Do)

Cloudflare’s emergency WAF rules are genuinely useful right now – they block the known exploit vectors for all customers, including free plans. But Cloudflare’s own CTO calls it a stopgap, and for good reason: the rules only help if your server accepts traffic exclusively through Cloudflare, and they only cover attack patterns that are known so far. New vectors are still being discovered. A WAF buys you time. Only the patch buys you safety.

The Bottom Line

PHP2Shell (CVE-2026-109618 and CVE-2026-109619) is about as serious as web vulnerabilities get: critical severity, leaked before the patch, already reproduced by researchers, with early attacks reportedly emerging and government services pulling themselves offline preemptively. If your site runs PHP, check your version today, and upgrade the moment your host ships the fixed build. And if you’re on PHP 5 or 7, treat this as your final nudge to migrate – the fix train left that station years ago.

Java has now had its own version of the same nightmare: read our Java4Shell coverage.

2 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *