Pavol Rašev
Available for remote contracts from December
Blog

Critical PHP vulnerability, October 2026: what it means for your website

On 21 October 2026 PHP released fixes for two critical flaws that let an attacker run code on a server without logging in. If your website or online store runs on PHP, it needs PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or newer. We have checked every client website we look after and secured the ones that needed it.

Critical PHP flaws, October 2026 Critical PHP flaws, October 2026 Is your site on a fixed version? CVE-2026-109618 · CVE-2026-109619 9.2 / 10 CVSS v4.0 · remote code execution 21. 10. 2026 PHP 8.5.12 8.4.27 8.3.36 8.2.35 pavolrasev.com

On Tuesday, 21 October 2026, the PHP project shipped an emergency release. Two flaws in PHP itself, not in WordPress, PrestaShop or any plugin, let an attacker run their own code on a web server with a single request and no login. Details leaked before the planned announcement, a proof-of-concept exploit is public, and security firms report the first attack attempts.

The short version: if your site runs on PHP, it needs one of the fixed versions, and no setting in your shop or CMS can replace the update.

What happened

The two flaws are tracked as CVE-2026-109618 and CVE-2026-109619, and both are rated 9.2 out of 10 (CVSS v4.0). The first comes from how PHP handles running out of memory in the middle of a request. The second lets data from one request survive into the next one on the same server process. In both cases the attack happens before the application’s own code runs, so a well-written shop doesn’t protect you.

Affected Every PHP version that serves web pages, through PHP-FPM, mod_php, CGI and others
Fixed in PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35 (released 21 October 2026)
PHP 8.1 and older No longer updated by the PHP project; only minimal backports exist for 7.4, 8.0 and 8.1
Workaround None that fully protects you. Settings like session.upload_progress.enabled=0 only narrow the attack
Note PHP 8.2 reaches end of life on 31 December 2026

What we did for our clients

We went through every website and online store we look after for our clients, checked which PHP version each one runs, and secured every site the flaw affected by updating PHP to a fixed version. Sites already on a fixed version didn’t need anything.

How to check and secure your site

If someone else looks after your website, ask them one question: which PHP version is it running today, and is it one of the fixed ones? If you manage it yourself:

  1. Find your PHP version in your hosting control panel, or ask your hosting provider. Don’t publish a phpinfo() page to check it.
  2. If it’s below 8.5.12, 8.4.27, 8.3.36 or 8.2.35 on its branch, update to the latest version of that branch. Most hosting panels let you switch the version in a few clicks.
  3. If you’re on PHP 8.1 or older, this is the moment to plan a move to a supported version. Older shops (PrestaShop 1.7, old WordPress themes and plugins) often need work before they run on new PHP, so test on a copy first.
  4. After the update, open the site, place a test order or send a test form, and check the error log.
  5. Until you can update, ask your host about the temporary settings from the PHP advisory. They reduce the risk but don’t remove it.

Sources