Products and stacks · Hosting platforms and server managers

PHP2Shell in Nexcess: is it affected and how to fix it

Quick verdict

Affected; a fix exists for some versions or components only.

Vendor status: Partly fixed
PHP: patched builds deploying · cPanel 8.2–8.5 + 7.4–8.1 backports · CloudLinux backports 5.2–8.5 · Plesk · cPanel/WHM: cPanel update + yum update
Last checked: 2026-10-22

Nexcess's status page incident “PHP Security Vulnerability Assessment (CVE-2026-109618 & CVE-2026-109619)” first said on 21 October that it was reviewing its hosting environments and putting mitigations in place; at 11:40 EDT (15:40 UTC) that day no patches had yet reached production systems. At 13:57 EDT (17:57 UTC) it said customers on cPanel/WHM could patch PHP 8.5, 8.4, 8.3 and 8.2, plus backported 8.1, 8.0 and 7.4, by running a cPanel update and then a yum update. Its latest update (22 October, 10:34 EDT, i.e. 14:34 UTC) says its engineering teams are deploying patched PHP builds across its hosting infrastructure and lists the same builds as Liquid Web’s status page: on cPanel EasyApache 4, 8.5.12, 8.4.27, 8.3.36 and 8.2.35 plus backports 8.1.34-5, 8.0.30-12 and 7.4.33-19; on CloudLinux EasyApache 4, backported builds for every branch from 5.2 to 8.5 (for example ea-php82 8.2.34-2 and ea-php85 8.5.11-2, version numbers below the upstream fix); on Plesk 18.0.81.4 and Windows Plesk, 8.5.12, 8.4.27, 8.3.36 and 8.2.35, with Plesk builds of 8.1, 8.0 and 7.4 dated 21 October. Check your build with a phpinfo() file and, if it is not patched, run a package update through the control panel; sites on end-of-life PHP should move to a supported version. Nexcess has not given a completion time.

How to check the PHP version Nexcess uses

Run the command for your setup. A version at or above 8.2.35, 8.3.36, 8.4.27 or 8.5.12 in its branch is fixed; older branches are fixed only by a vendor build that says so.

php -v

The command-line php can differ from the PHP that serves the site. To be sure, check the web SAPI (a temporary phpinfo() page behind authentication, or the panel's PHP settings) and remove it afterwards. Our version checker compares a version number for you.

🔎 Got a version number? Paste it into the PHP2Shell checker →

How to fix PHP2Shell in Nexcess

Find out where the PHP that runs this application comes from: your distribution, a third-party repository (Ondřej Surý, Remi), a hosting panel, a Docker image or your host.
Update that PHP to 8.2.35, 8.3.36, 8.4.27, 8.5.12 or a vendor build with the backported fix, and restart every PHP worker.
On shared or managed hosting you cannot patch PHP yourself: ask the host whether the fixed PHP is deployed, and switch the site to a fixed version in the panel.
If the site still runs PHP 8.1 or older, move it to a supported branch; PHP published only source patches for 7.4, 8.0 and 8.1.

Prefer to let an AI agent do the checks? Check if you are affected · Fix with an AI agent

If you cannot patch yet

Set session.upload_progress.enabled = 0 where applications cannot override it (php.ini, php_admin_value in the FPM pool or Apache config), and restart PHP.
On PHP 8.5, set fatal_error_backtraces = 0.
PHP's interim advice also covers memory_limit and a low post_max_size; follow the remediation page exactly, because these settings only reduce some paths.
Restrict access (VPN, IP allowlist) or take the service offline if it runs PHP 8.1 or older with no vendor backport. WAF rules help but are not a fix.

FAQ

Is Nexcess affected by PHP2Shell?

Affected; a fix exists for some versions or components only. Nexcess's status page incident “PHP Security Vulnerability Assessment (CVE-2026-109618 & CVE-2026-109619)” first said on 21 October that it was reviewing its hosting environments and putting mitigations in place; at 11:40 EDT (15:40 UTC) that day no patches had yet reached production systems. At 13:57 EDT (17:57 UTC) it said customers on cPanel/WHM could patch PHP 8.5, 8.4, 8.3 and 8.2, plus backported 8.1, 8.0 and 7.4, by running a cPanel update and then a yum update. Its latest update (22 October, 10:34 EDT, i.e. 14:34 UTC) says its engineering teams are deploying patched PHP builds across its hosting infrastructure and lists the same builds as Liquid Web’s status page: on cPanel EasyApache 4, 8.5.12, 8.4.27, 8.3.36 and 8.2.35 plus backports 8.1.34-5, 8.0.30-12 and 7.4.33-19; on CloudLinux EasyApache 4, backported builds for every branch from 5.2 to 8.5 (for example ea-php82 8.2.34-2 and ea-php85 8.5.11-2, version numbers below the upstream fix); on Plesk 18.0.81.4 and Windows Plesk, 8.5.12, 8.4.27, 8.3.36 and 8.2.35, with Plesk builds of 8.1, 8.0 and 7.4 dated 21 October. Check your build with a phpinfo() file and, if it is not patched, run a package update through the control panel; sites on end-of-life PHP should move to a supported version. Nexcess has not given a completion time.

Does updating Nexcess itself fix CVE-2026-109618 and CVE-2026-109619?

Only if the update contains fixed PHP. PHP2Shell is a flaw in the PHP interpreter, so what matters is the PHP that Nexcess runs on. Check the version after updating.

Which PHP versions fix PHP2Shell?

PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12, released 21 October 2026. PHP 8.1 and older get no release from the PHP project; only vendor builds with a backport (or a self-built source patch for 7.4, 8.0 and 8.1) fix them.

What if Nexcess has no fix yet?

Keep its PHP-based web interface off the internet (VPN or IP allowlist), apply PHP's interim settings such as disabling session upload progress, and install the vendor update as soon as it ships. Interim settings reduce risk but are not a fix.

← All products that bundle PHP

Sources

Outbound links leave this site. We do not host exploit code.

Unofficial summary of public sources. This site is not affiliated with the vendor or the PHP project and hosts no exploit code.