Critical PHP vulnerabilities of October 2026: what to do now
PHP vulnerability CVE-2026-109618 and CVE-2026-109619 in plain English: who is affected, how to check your PHP version, and which update to install now.


On 21 October 2026, the PHP project published an advisory titled “Critical remote code execution vulnerabilities, update now”. PHP runs a large share of business websites, online shops, client portals and intranets, so this PHP vulnerability is likely to concern you even if you have never chosen PHP yourself: your website, your WordPress site or a business application may run on it.
This article explains in plain language what the two flaws are, who is affected, how to check which PHP version you run, and what to do this week, whether you manage your own server or rely on a hosting company or a supplier.
This article gives general, practical information as of 23 October 2026 (exploitation status updated on 5 November 2026), based on the official sources listed at the end. It does not replace the advice of a security professional, and the situation can change quickly: check the PHP advisory and your vendor’s advisories for updates.
What happened: two critical flaws in PHP itself
PHP is the programming language that runs on the web server and builds the pages your visitors see. The two flaws are not in a plugin or a theme: they are in PHP’s core, so they concern applications written in PHP whatever their own code looks like.
| CVE-2026-109618 | CVE-2026-109619 | |
|---|---|---|
| Short name (PHP advisory) | RCE via OOM corruption | RCE via stale global state |
| Severity | CVSS v4.0 9.2, critical | CVSS v4.0 9.2, critical |
| Published | 21 October 2026 | 21 October 2026 |
| Fixed in | PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 | PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 |
A CVE (Common Vulnerabilities and Exposures) number is the public identifier of a security flaw. The CVSS (Common Vulnerability Scoring System) score rates its severity from 0 to 10: 9.2 is in the “critical” band. RCE stands for remote code execution: an attacker on the internet can make your server run their own commands.
In everyday words:
- CVE-2026-109618: when a request uses up all the memory PHP allows it (an “out of memory” error, or OOM), PHP can stop halfway through preparing its internal data. The clean-up that follows may then treat that half-prepared data as valid.
- CVE-2026-109619: a PHP worker handles one request after another. Some internal information from a previous request can survive after its memory has been freed, and the next request may use it before it is reset.
In both cases, a carefully crafted request can turn this confusion into control of the server. According to the PHP advisory, the attacker does not need an account, and with Apache’s mod_php a demonstrated exploit works before any of your application’s code runs. We will not go further into the technical detail: the advisories linked below have it, and you do not need it to act.
Who is affected by this PHP vulnerability
The PHP advisory says that all PHP installations serving web requests are at risk, whatever the way PHP is connected to the web server: PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. It considers the risk highest for mod_php.
In practice, you are concerned if:
- your website or online shop runs on PHP, which includes WordPress, Drupal, Joomla, Magento, PrestaShop and most sites built with Laravel or Symfony;
- a business application, client portal or intranet you use was developed in PHP;
- your hosting plan is a shared or managed hosting offer with PHP, such as a cPanel account.
The versions affected, according to the PHP security advisories on GitHub, are all versions before 8.5.12, 8.4.27, 8.3.36 and 8.2.35 in each of these four branches. PHP 8.1 and older no longer receive updates from the PHP project: they are not on that list because no official release will fix them.
Is it being exploited? Yes, according to CISA. When we published on 23 October 2026, the PHP advisory did not report attacks in the wild and neither CVE was in the Known Exploited Vulnerabilities (KEV) catalogue of the US Cybersecurity and Infrastructure Security Agency (CISA). On 26 October 2026, CISA added both CVEs to that catalogue, which lists flaws for which it has evidence of exploitation. In its alert on the PHP flaws, revised the same day, CISA advises organisations that cannot update immediately, or that still use PHP 8.1 or older, to take their PHP-based systems offline until they are patched or updated. As of 5 November 2026, neither CISA’s alerts nor the PHP advisory describe these attacks. What to do has not changed: update now, starting with the sites open to the internet.
How to check your PHP version
You need the exact version number, for example 8.3.35 or 8.4.27, not just “PHP 8”.
On shared or managed hosting
In cPanel, open Select PHP Version or MultiPHP Manager: each site shows its PHP version. Other control panels have a similar page, often under “PHP settings”. If several sites share the account, check each one: they can use different versions.
On your own server
Run php -v in a terminal. Be careful: the command-line PHP can differ from the PHP that serves your website. To see the version the web server really uses, create a temporary file containing <?php phpinfo();, open it in your browser, note the version at the top, then delete the file at once, because it shows details about your server.
When a Linux distribution provides PHP
Distributions such as Debian, Ubuntu or Red Hat Enterprise Linux sometimes fix a flaw without moving to the PHP project’s version number. The number alone is not enough: look for your distribution’s security notice for CVE-2026-109618 and CVE-2026-109619. Debian, for example, published DSA-6574-1 for Debian 13 and DLA-4848-1 for Debian 12.
When a supplier runs the application for you
Ask them in writing which PHP version runs your application, on which server, and when they will update it. A good supplier answers within the day.
What to do now
1. Update PHP
The only complete fix is to update to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or to the patched package of your distribution. Restart PHP afterwards (PHP-FPM, Apache or the service your server uses), so that no old worker stays in memory. On shared hosting, the hosting company often updates the patch versions itself: check the version number, and ask their support if it has not changed.
2. If you are on PHP 8.1 or older
There is no official release for these versions. Your options, in order of preference:
- move to a supported branch (8.4 or 8.5 gives you the most time), after testing your application on it;
- use the fixed packages of your distribution or of a paid long-term support (LTS) vendor, if they provide them;
- as a last resort, build PHP from source with the minimal fixes the PHP security team published for 7.4, 8.0 and 8.1.
Moving an old application to a recent PHP version can break things. This is often the moment to look at the wider question of an ageing application, the subject of our guide to technical debt and modernisation.
3. If you cannot update today
The PHP advisory lists temporary measures, such as setting memory_limit=-1 in a way applications cannot override, a low post_max_size, and session.upload_progress.enabled=0. It is explicit: they reduce exposure to some attack paths but do not make an installation safe. Apply them only to buy a few days, with the advisory in front of you, and plan the update.
4. Plan the next one
PHP 8.2 reaches its end of life on 31 December 2026, according to the PHP advisory: after that date, it will receive no more security fixes. If you are on 8.2, schedule the move to a newer branch now rather than in an emergency.
Checklist for this week
- List every website and application that runs on PHP, with its hosting and its owner.
- Note the exact PHP version of each, as the web server uses it.
- Update to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or install your distribution’s fixed package.
- Restart PHP and check the version again.
- Ask your hosting company and suppliers for a written confirmation.
- For PHP 8.1 or older: decide between upgrade, vendor support and source patches.
- For PHP 8.2: plan the move before 31 December 2026.
- Add PHP to the list of software whose updates you follow, as recommended in our essential cybersecurity measures for SMEs.
How we can help
AnazTech is not a managed security provider and does not handle incidents. If one of your PHP applications cannot simply be updated, because it is old, undocumented or its supplier has disappeared, that is our work: an IT audit of the application, then its upgrade or its rebuild, through our modernisation expertise. We also build and maintain business web applications with updates planned from the start.
Official sources
- PHP project: Security advisory: Critical remote code execution vulnerabilities, update now (21 October 2026)
- PHP security advisories on GitHub: GHSA-w8hw-w9fx-j79w and GHSA-6wmf-4rv5-p3rp
- US National Vulnerability Database (NVD): CVE-2026-109618 and CVE-2026-109619
- CISA: Known Exploited Vulnerabilities catalogue and alert Critical Vulnerabilities in PHP Require Immediate Patching (21 October 2026, revised 26 October 2026)
- Cisco: Vulnerabilities in PHP Affecting Cisco Products: October 2026
- Debian: security tracker for CVE-2026-109618
Frequently asked questions
Is my WordPress site affected by the PHP vulnerability?
Probably, if its PHP version is older than the fixed releases: WordPress runs on PHP, and these flaws are in PHP itself, not in WordPress. Updating WordPress or its plugins does not fix them. Check the PHP version in your hosting control panel, and ask your hosting company to update it if it is below 8.5.12, 8.4.27, 8.3.36 or 8.2.35.
My hosting company manages PHP. Do I have anything to do?
Yes: check. Many hosting companies update patch versions themselves, but not always on the same day, and some accounts are pinned to an old branch such as 8.1. Look at the exact version in your control panel. If it has not changed, or if your site uses PHP 8.1 or older, contact their support and ask for the date of the update.
Does a web application firewall protect me?
It can block some known attack patterns, but it is not a fix. The PHP advisory says that only an update is a complete solution, and the temporary measures it lists do not make an installation safe. Treat a firewall as an extra layer while you update, never as a reason to postpone the update.
In short
Two critical flaws in PHP itself, CVE-2026-109618 and CVE-2026-109619, can let an attacker run commands on a server without an account. They are fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Check the exact PHP version of every site and application this week, update, restart and confirm. For PHP 8.1 and older, the update becomes an upgrade project.
An old PHP application that nobody dares to update? Book a free 30-minute discovery call: we look at it together and decide where to start.
Related servicesWebsites and web appsModernisation
Let’s talk about it on a 30-minute discovery call, free and with no obligation.
Get our next articles in your feed: follow AnazTech on LinkedIn.Follow on LinkedIn






