Update, 23 Oct: PHP has published a follow-up advisory for a separate, unlikely remote code execution issue, CVE-2026-115560, which affects only applications that switch session.serialize_handler to php at runtime with ini_set() while session upload progress is enabled. There is no fix release yet, as PHP will address it in the next regular bugfix release. Until then, PHP suggests setting session.upload_progress.enabled=0, the same mitigation listed on 21 Oct, so if you already applied it no further action is needed [7].
On 21 October 2026 the PHP project released emergency security updates for two critical flaws, tracked as CVE-2026-109618 and CVE-2026-109619 and widely called "php2shell". Both can let an attacker who has no login run their own code on a server running PHP. If your business runs anything built on PHP, from a website to an internal portal or a customer marketplace, this is a patch to treat as urgent.
What happened
PHP announced on 20 October that a security release was coming, and shipped it the next day in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35 [1][2]. The two flaws sit in parts of PHP that almost every web request touches.
The PHP security team rates both 9.2 out of 10 (CVSS 4.0) [2]. On Apache with mod_php, a single unauthenticated request can trigger the first flaw before any of your own application code runs, and full remote code execution was shown with default settings [3]. Remote code execution was also confirmed on PHP-FPM through application code paths [3].
On 21 October the US Cybersecurity and Infrastructure Security Agency urged organisations to patch immediately. At that time it had not seen the flaws being exploited [5]. CERT-EU noted the same day that technical details and early proof of concept code were circulating publicly, which makes attacks more likely [2]. CERT/CC published its own vulnerability note on 22 October [6].
Who is affected
According to the PHP project, every PHP installation that serves web requests is at risk [1]. That includes:
Affected versions are PHP 8.5 before 8.5.12, 8.4 before 8.4.27, 8.3 before 8.3.36 and 8.2 before 8.2.35 [2][4]. PHP 8.1 and older are end of life and get no official release, so they stay exposed unless you apply a backport or upgrade [1].
PHP is also built into a lot of other software. You may be running it inside a content system, an admin panel, a hosting control panel or a bought in product without knowing it [2][5].
How to check if you are exposed
php -v to see the command line version, and check the version your web server actually uses, for example with a protected phpinfo() page that you remove straight afterwards, or your hosting dashboard.How to patch
The bigger lesson
Systems stuck on old PHP versions are the hardest to protect when a flaw like this lands, because there is no official patch to apply. If an older PHP application is holding your business back, a planned move to a supported, modern stack costs far less than an emergency. Souza Labs helps teams in the UAE, GCC and UK modernise legacy systems step by step. Book a free consult, or message us on WhatsApp at +971 585692165.