| |

PHP Security Update, October 2026: What Hosting Customers Should Do

Close-up of servers in a data center server room

Short answer: On 21 October 2026 the PHP project shipped a PHP security update (8.5.12, 8.4.27, 8.3.36 and 8.2.35) that fixes two critical flaws, CVE-2026-109618 and CVE-2026-109619, which can allow unauthenticated remote code execution. Move every site to a supported, patched PHP branch. PHP 8.1 and older get no official fix.

If you host websites, this one is worth ten minutes of your day. Below: what changed, who is exposed, how to see which PHP version your sites run in cPanel, and what resellers should check across their client accounts.

What did the October 2026 PHP security update fix?

Two bugs in PHP’s core, both rated critical by the PHP team and both able to run attacker code without a login.

According to the PHP security advisory on php.net:

  • CVE-2026-109618 (GHSA-w8hw-w9fx-j79w): when PHP runs out of memory mid-request, request data can be left half-built, and cleanup may then treat that broken data as valid.
  • CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp): some internal state tied to a request can outlive the memory behind it, so the next request on the same worker may read stale data before it gets reset.

The PHP team lists PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed as affected, which covers nearly every way PHP serves a website. It calls the risk highest for mod_php, where it says a demonstrated exploit works before any of your application code runs.

PHP branch Patched release Status (php.net)
8.5 8.5.12 Supported
8.4 8.4.27 Supported
8.3 8.3.36 Security fixes only
8.2 8.2.35 Security fixes only, end of life 31 Dec 2026
8.1 and older No official release End of life

The PHP team did publish minimal source backports for 7.4, 8.0 and 8.1, but those are for people who compile PHP themselves. On shared and reseller hosting you won’t be building from source, so treat 8.1 and below as unpatched.

Why does a PHP security update matter on shared hosting?

Because the exploit doesn’t need your WordPress, WHMCS or custom code to have a bug. The weakness sits in PHP itself, so a fully updated plugin list doesn’t protect you if the PHP underneath is old.

That’s also why the PHP team’s own wording is blunt: “updating is the only safe choice.” Configuration tweaks reduce some attack paths, but the advisory says they “do not make an installation safe.”

How do I check which PHP version my site uses in cPanel?

Log in to cPanel and open MultiPHP Manager (under Software). It lists each domain with the PHP version assigned to it.

A few things to look at while you’re there:

  1. The version per domain. Anything showing PHP 8.1, 8.0 or 7.x is on a branch that won’t get this fix.
  2. “Inherit” entries. A domain set to inherit uses the server default, so its real version depends on what the host has set.
  3. Your app’s requirements. Before switching, check what your CMS or script supports. WordPress, WHMCS and most Laravel apps publish their supported PHP versions.

If your host uses CloudLinux, you may see a Select PHP Version page instead. Same idea: pick a supported branch per account.

Want to confirm the exact patch number? Create a temporary info.php file containing <?php phpinfo();, open it in a browser, read the version at the top, then delete the file straight away. Don’t leave it online.

How do I switch to a patched PHP version?

In MultiPHP Manager, tick the domain, choose a supported version (8.3, 8.4 or 8.5) from the dropdown and apply. The change takes effect within seconds.

Then test:

  • Load the home page and a few inner pages.
  • Log in to the admin area and save something.
  • Submit a contact form or test checkout if you run a shop.
  • Check error_log in the site folder for new warnings.

If something breaks, switch back, note the error, and update the plugin or theme that caused it before trying again. Going back to 8.1 for good isn’t a safe resting place after this release.

The patch level itself (say 8.3.35 to 8.3.36) is installed by whoever manages the server, not from MultiPHP Manager. On cPanel servers PHP comes from EasyApache 4 packages such as ea-php83, so if you run your own VPS with WHM, update those packages through WHM or your package manager and restart PHP-FPM.

What should resellers check for their clients?

Resellers carry this for every account under them, so a quick audit beats waiting for a client to ask.

In WHM, MultiPHP Manager shows the PHP version for every domain your reseller account controls, and lets you change several at once. A sensible order:

  1. Export or note every domain still on 8.1 or older. These are your highest-risk accounts.
  2. Tell those clients what’s changing and when. A short email with the date of the switch and a request to test their site is enough.
  3. Move them to 8.3 or newer and ask them to check their admin area and forms.
  4. Flag 8.2 sites for a second move. PHP 8.2 is patched today, but php.net lists its end of life as 31 December 2026, so those sites need another upgrade within ten weeks.

If a client’s site won’t run on a supported PHP version, that’s usually an outdated theme, plugin or custom script. That’s worth a conversation about updating the code rather than keeping a vulnerable PHP version alive.

What if I can’t update right away?

The advisory lists stopgaps, such as lowering post_max_size and turning off session.upload_progress.enabled, but they only block specific known paths. On shared hosting you usually can’t set them at the level the advisory requires anyway (it warns against relying on ini_set() or .user.ini). Switching versions in MultiPHP Manager is faster and actually fixes the problem.

Moving hosts because your PHP is stuck?

If your current host can’t offer a supported PHP version, moving is a reasonable answer. ResellerBytes offers free website migration, so you can test your site on a current PHP branch without rebuilding it.

FAQ

Which PHP versions fix CVE-2026-109618 and CVE-2026-109619?
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, all released on 21 October 2026, per php.net.

Is PHP 8.1 safe if I keep it updated?
No. PHP 8.1 is end of life, and the PHP project did not issue an 8.1 release for these flaws. Move to 8.3 or newer.

Does changing PHP in MultiPHP Manager install the patch?
It changes which PHP branch a domain uses. The patch release inside that branch is installed by the server administrator through system updates.

Will switching PHP versions break my WordPress site?
Usually not on a current WordPress install. Old plugins and themes are the common cause of errors, so test after switching and keep the old version handy to roll back while you fix them.

Is PHP 8.2 good enough?
For now it’s patched, but php.net lists 31 December 2026 as its end of life. Plan to move to 8.3 or later before then.


Sources: PHP news archive 2026, PHP 8 ChangeLog, PHP supported versions. Last checked 22 October 2026.

Share this content:

Leave a Reply

Your email address will not be published. Required fields are marked *