PHP2Shell: The Unauthenticated RCE That Put Every Omani PHP Server on the Clock
On 21 October 2026 the PHP team shipped fixes for two critical remote code execution flaws affecting PHP 5.4 through 8.5. There are no complete mitigations — only upgrading. Here is what that means for teams running PHP in Oman.

What was actually disclosed
On 21 October 2026 the PHP development team released PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 to fix two critical vulnerabilities that allow unauthenticated remote code execution. The pair has been given the informal name PHP2Shell, and both carry a CVSS score of 9.2. CVE-2026-109618 is described by the PHP team as RCE via out-of-memory corruption: an out-of-memory condition can interrupt PHP while internal request data is only partially initialised, and request cleanup may then treat that invalid data as valid. CVE-2026-109619 is RCE via stale global state: request-owned internal state can survive after the memory backing it has been freed, and a later request handled by the same worker may then use it. Both are flaws in the PHP runtime itself, not in a framework, a CMS or a library. Any PHP application is affected by virtue of the interpreter it runs on, regardless of how carefully the application code was written.
Why the usual stalling tactics do not apply here
Most vulnerability announcements come with an interim mitigation — disable a module, add a rule at the edge, restrict a path — that buys a maintenance window. This one does not. The PHP advisory is unusually direct on the point: there are no complete mitigations, updating is the only safe choice. That sentence should change how the work is scheduled. A web application firewall in front of the application does not remove the condition, because the flaws are in how the interpreter handles its own memory across requests. The practical consequence for an operations team is that the patch cannot wait for the next quarterly maintenance cycle, and there is no configuration change that justifies deferring it.
The end-of-life problem, which is the real story in Oman
No official fixed builds were published for PHP 7.4, 8.0 and 8.1, because those branches are end of life. Affected, but not fixed. This is where the exposure concentrates for Omani organisations. Line-of-business PHP applications in this market are frequently long-lived: a payroll or inventory system commissioned years ago, a customer portal that has been stable enough that nobody revisited the runtime, a government-facing integration that nobody wants to touch because it works. Those systems are the ones most likely to be sitting on an unsupported PHP branch, and they are now permanently exposed to an unauthenticated RCE with no vendor patch coming. The only remedy for those systems is a runtime upgrade, which usually means a compatibility assessment first. Code written for PHP 7.x will often need work before it runs cleanly on 8.3 or 8.4 — removed functions, stricter type handling, changed defaults.
Two more items from the same fortnight
Two further issues landed close enough to be part of the same patch cycle, and both are easy to miss. On 23 October the PHP team published an advisory for CVE-2026-115560 without a release. The interim guidance is to set session.upload_progress.enabled=0 and restart every worker, with a full advisory promised alongside the next regular bugfix release. If you patched on 21 October and considered the matter closed, this one is still outstanding. On 26 October the team shipped updated Windows builds — PHP 8.5.12-1, 8.4.27-1, 8.3.36-1 and 8.2.35-1 — carrying Brotli 1.2.1 to fix CVE-2026-111497, an out-of-bounds write in Brotli decompression. The PHP runtime version is unchanged in those builds, so a version check alone will not tell you whether a Windows host is patched.
A note on scope that is easy to get wrong
CVE-2026-111497 is a Brotli flaw, not a PHP flaw. The same vulnerability was patched in Node.js on the same day, because both runtimes bundle the same decompression library. If your estate runs both PHP and Node, this is one dependency issue presenting in two places, and patching one does nothing for the other. Checking only the obvious runtime is how half an estate stays vulnerable.
What a sound response looks like
Inventory first: every host, container image and CI runner that executes PHP, with its exact version. Estates almost always contain more PHP than the team remembers — a legacy admin tool, a staging box, a vendor appliance. Patch the supported branches immediately to 8.5.12, 8.4.27, 8.3.36 or 8.2.35. Treat anything on 7.4, 8.0 or 8.1 as an incident rather than a maintenance item, because no patch is coming for it. Apply the session.upload_progress mitigation for CVE-2026-115560 until the next bugfix release, and on Windows confirm you are on the -1 rebuilds rather than relying on the PHP version string. Then look backwards. An unauthenticated RCE that was exploitable before you patched means patching closes the door but does not establish whether anyone came through it. Review web server logs, check for unexpected files in writable paths, and verify scheduled tasks and outbound connections. Finally, note the date: PHP 8.2 reaches end of life on 31 December 2026. Patching to 8.2.35 is a correct emergency action and a poor destination. Anyone landing there should be planning the move to 8.3 or 8.4 now.
How IIT Oman can help
This is work we do for organisations across Oman and the GCC. A runtime and dependency audit across your estate establishes what you are actually running, including the systems nobody has logged into for a year. For applications stranded on end-of-life PHP, we carry out compatibility assessments and incremental upgrades that keep the system running while the runtime moves underneath it, rather than a rewrite nobody can fund. Where an exposure window existed, our cybersecurity practice performs compromise assessment and digital forensics to establish whether the flaw was used before it was closed. And for teams that would rather not be in this position again, we set up patch pipelines and dependency monitoring so the next critical advisory is a scheduled afternoon rather than a scramble. If you are unsure what PHP versions are running across your organisation, that uncertainty is the finding. Talk to our engineering team in Muscat and we will help you establish the answer.

