PHP Has Released the Patch: How to Update to 8.5.12, 8.4.27, 8.3.36 or 8.2.35 Without Improvising

On Wednesday, October 21, the PHP team released the fixed versions it had announced a day earlier. Its official security advisory asks all users to update immediately: the two flaws, tracked as CVE-2026-109618 and CVE-2026-109619, can allow unauthenticated remote code execution. In plain words, someone on the internet could run instructions on your server without needing an account. We already covered the advance notice; this is the guide to actually carrying out the update.
Which versions to install
According to the php.net advisory, the fixed versions are:
- PHP 8.5.12
- PHP 8.4.27
- PHP 8.3.36
- PHP 8.2.35
The advisory applies to every PHP installation serving web requests: PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. The PHP team rates the risk highest for mod_php, where they have a demonstrated exploit in which an unauthenticated request triggers the attack before any application code runs. The key sentence: "there are no complete mitigations, updating is the only safe choice."
What the two flaws are
The advisory describes them as follows:
- CVE-2026-109618, remote code execution via out-of-memory (OOM) corruption: out-of-memory handling can interrupt PHP while internal request data is only partially initialized, and the later cleanup treats that invalid data as valid.
- CVE-2026-109619, remote code execution via stale global state: internal request state can survive after its memory has been freed, and a later request handled by the same worker uses it before it is reset.
You don't need to follow the technical detail to act. What matters is that the advisory sets no special condition on the victim's side beyond running PHP to serve pages.
How to update, depending on your case
- Linux server you manage yourself: the advisory says distributions and long-term-support (LTS) vendors received the patches in advance. Check your package manager for new packages, apply them and restart PHP-FPM or Apache; without a restart the old processes stay in memory.
- Shared or managed hosting: write to your provider and ask for written confirmation of the PHP version and that the patch is applied.
- Windows: binaries are on the php.net downloads page.
- PHP 8.1 or older: the PHP project no longer publishes updates for those branches. Some LTS vendors provide their own fixes, so ask yours; otherwise you need to migrate to a supported version. Given the severity, the PHP security team also provided minimal source backports for PHP 7.4, 8.0 and 8.1 for people who build from source.
If you can't update today
The advisory is clear that these measures reduce exposure but do not make an installation safe. They are a bridge of hours, not a solution:
- For the first flaw: set
memory_limit=-1in a way applications cannot override, and lowerpost_max_size(8M if no uploads are needed; 32M if they are, keepingupload_max_filesizebelow it). - For the second: set
session.upload_progress.enabled=0inphp.inior in the pool or server configuration, and restart every worker.
The full details and caveats (for example, don't use system-level memory limits, which can trigger the very failure) are in the official advisory; read them before touching production configuration.
What this means for your SME
- Do a 10-minute inventory: which of your systems use PHP? Website, online store, intranet, the custom invoicing system, the customer portal. If you don't know, ask whoever built or hosts it.
- Ask for a date, not a promise: ask your provider for the installed version and the date of the patch.
- An end-of-life version means accumulating risk. The PHP 8.2.35 release announcement states that PHP 8.2 reaches end of life on December 31, 2026; plan the migration to a newer branch now instead of waiting for the next emergency.
- Check what may already have happened: if your server was exposed without the patch, review access and error logs and rotate credentials stored in configuration files if you see odd activity.
How We Approach It at SimCodec
At SimCodec we do exactly this work for other companies: system inventories, server updates, monitoring and backups so you can roll back if an update goes wrong. If you want us to check which version your site or system runs and how much risk you carry, write to us. To harden the rest of your security, see our guide to Zero Trust cybersecurity for SMEs.


