Skip to main content

Morgan Cyber Solutions

This is a developing story. Details below are based on early, unverified reporting and will be updated as official advisories are published.

2026-10-20 23:00 – Initial Post

A critical remote code execution vulnerability in PHP, tracked as CVE-2026-109618 (with a companion flaw, CVE-2026-109619), is reportedly about to be disclosed publicly. According to early reporting, the issue affects every version of PHP from PHP 5 onward. If confirmed, that would put an enormous slice of the internet in scope at once.

I want to be straight with you; as of writing, this is still an evolving situation. No official advisory, patch, or severity score has been published, and the full technical details are not yet public. We are sharing this now because the window to prepare is short, and the organisations that act before disclosure are the ones that patch within hours instead of days.

What we know so far

Here is the current picture, separating what is reported from what is confirmed:

Detail Status
CVEs CVE-2026-109618 and CVE-2026-109619 (RCE)
Versions affected Reportedly all versions, PHP 5 onward (unconfirmed)
Fixed versions None published yet
Severity (CVSS) Not yet scored
Exploited in the wild None reported as of 21 Oct 2026; not in CISA KEV
Official advisory Expected 22 Oct 2026, ~18:00 CEST

Treat the “all versions” claim with appropriate caution. It originates from early, unverified reporting rather than a vendor advisory. That said, planning for the worst case here costs little and buys you time. The sensible assumption until proven otherwise is that anything running PHP is potentially in scope.

Why the blast radius is so large

PHP is not a niche technology. It still powers a very large share of the world’s websites and web applications. WordPress alone, which is built on PHP, sits behind a huge proportion of the internet. That is before you count Drupal, Joomla, Laravel apps, bespoke internal tools, and countless line of business systems.

A vulnerability that spans “all versions from PHP 5 onward” is unusual precisely because it ignores the normal safety net. Most serious bugs affect a window of versions, so a reasonably current estate is often fine. If this one truly reaches back to PHP 5, then legacy systems that have been quietly running untouched for years, the ones nobody wants to reboot, are exposed alongside modern, fully patched deployments.

The part that is easy to overlook: PHP does not only run your public website. It frequently sits underneath things you would never think of as “a PHP app”: the admin console of an appliance, a vendor’s web management portal, an SSL VPN login page. That is where this gets interesting for infrastructure teams.

Your WordPress site probably isn’t the real problem

When a PHP vulnerability makes the news, the first reaction for most organisations is to look at their website. That makes sense, because so many sites run on WordPress, and WordPress runs on PHP. But here is the point worth pausing on: your public website is probably not the most sensitive PHP system you own.

If your public website gets taken over, it does not look great. Nobody wants a defaced homepage or an embarrassing headline. But if you have built things sensibly, your public facing website is hosted away from your core infrastructure. It has no route to your sensitive data or PII. A compromise there is painful, not catastrophic.

The systems that should worry you more are the ones running PHP that can reach sensitive data or perform sensitive functions. Your CRM platform, full of customer records? The web interfaces used to manage your IT infrastructure, your firewalls, your VPNs, your appliances? Those are the places where a PHP flaw stops being an embarrassment and becomes a genuine breach. Spend your attention there first.

The vendor question: what’s running under the hood?

Here is an honest caveat is most IT infrastructure and security vendors do not publicly document what their products run internally. You will rarely find a datasheet that says “our management interface is written in PHP.” So what follows is informed suspicion, not confirmed fact.

When we look at the historic vulnerability reporting, the CVEs, the advisories, the independent security research, a number of well known vendors have shown signs over the years of PHP sitting in their management or SSL VPN web layers. Based on that track record, these are the kinds of products we would be looking at carefully:

To be absolutely clear: none of these vendors has been confirmed as vulnerable to CVE-2026-109618. We are flagging them because, if the “all versions” claim holds and any of these products do use PHP in the way historic reporting suggests, their internet facing and internal management interfaces could be a high value target. That uncertainty is exactly why the next point matters more than ever.

What to do now

You cannot patch a vulnerability that has not been published yet, but you can make sure that when the fix lands, you are ready to move within hours rather than days. Here is the prioritised prep work we are recommending to our customers:

Prepare for the patch

The bottom line

We don’t yet know the full scope of CVE-2026-109618. We don’t yet know which vendors will turn out to be affected. What we can say is that the fundamentals matter more than ever.

The controls that matter

There are a few key security controls at play here. They are exactly the ones we routinely find companies missing when we run a SURE assessment against them:

Why it is worth getting right

Get even a few of these right and a PHP flaw buried in a management portal becomes far harder for an attacker to reach, both for this CVE and for the next unknown one after it.

This is a developing situation, and we will update this post as official advisories and patches are released. If you would like help inventorying your PHP estate, locking down your management interfaces, or preparing a rapid patch plan, get in touch. We would rather help you prepare now than respond later.

2026-10-21 07:45 – Update

More detail is now available this moring:

The practical takeaway has not changed, it has just become more urgent. Know what you are running, get supported versions patched the moment the release lands, and get anything unsupported off the wire. We will keep updating this post as the official release notes and version numbers are confirmed.

2026-10-21 10:30 – Update

I have created a short video that talks through some of the content in this post.

2026-10-21 12:45 – Update

The story has moved from researcher chatter to official government guidance, which is a meaningful shift.

Since the guidance landed

Since that guidance landed, the picture has sharpened further, reported by Reuters:

The common thread

The thread running through the PHP team, the NCSC and the EU is consistent. Get your inventory done, be ready to patch the moment the release lands, and be prepared to pull exposed systems offline if you cannot patch in time. If you have not had the offline conversation with your leadership yet, have it today.

Sources for this update: NCSC: critical security issue affecting PHP and Reuters: EU agency warns websites may need to be taken offline.

2026-10-21 14:20 – Update

With the official patch still pending, code claiming to exploit these vulnerabilities is now circulating publicly, and a demonstration exploit chain known as php2shell has been shown off ahead of the release. A note of caution: security vendors including Tenable have not verified that the circulating code actually works against either CVE, and they warn that unverified exploit code often carries malware. So this is not an invitation to go looking for it or run it.

The takeaway is simpler and more urgent than the detail. Working exploit material is appearing before the fix is even out, which is the worst possible sequencing for defenders. Patch the moment the release lands, and keep exposed systems restricted or offline until you can.

2026-10-21 14:45 – Update

The fix is out. PHP has released 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and all PHP users are strongly encouraged to update immediately. Both CVE-2026-109618 and CVE-2026-109619 are confirmed as critical flaws allowing unauthenticated remote code execution.

If you cannot update yet

If you genuinely cannot update right away, PHP has published interim hardening measures that reduce exposure to specific attack paths. But it is explicit that these are not a complete fix and only an update makes an installation safe. Those settings are set out in the official release notes and advisories.

The bottom line: the fix is here, exploit material is already circulating, and researchers expected mass exploitation within minutes of release. This is now firmly a patch now situation. Identify your PHP, apply the update everywhere it runs, and prioritise anything internet facing and anything running mod_php.

Sources for this update: PHP official release and the advisories GHSA-w8hw-w9fx-j79w and GHSA-6wmf-4rv5-p3rp.

2026-10-22 08:15 – Update

Cloudflare’s own figures capture the curve better than anything. Its CEO, Matthew Prince, reported on X that across the Cloudflare network they saw thousands of exploit attempts in the 10 hours before public disclosure, jumping to tens of thousands within 45 minutes of the announcement, hundreds of thousands within two hours, and millions by today.

A day on from the patch, this is roughly where I expected to be, and it is a useful reminder of why the fundamentals matter. The wave people braced for largely materialised, but the sky has not fallen for those who were ready.

What happened overnight

Vendors and the wider response

The shrinking window

The honest lesson from the night is not a dramatic one. The organisations that had an inventory, patched quickly, restricted their management interfaces and assumed breach are the ones who slept fine. The ones scrambling this morning are mostly those still trying to work out where they even run PHP. If you patched yesterday, well done. If you did not, treat anything exposed and unpatched as already probed: patch it now, check your logs for the indicators the researchers are publishing, and get your management interfaces off the open internet. We will keep watching and update again if the exploitation picture changes materially.

Sources for this update: Ellio: what we observed and Tenable php2shell FAQ.