Official 2026 retail dates & mega-sales for 12 countries with .ics sync.
Get calendar →
7 min readBy the OH Digital team
Back to blog

CVE-2026-109618 and CVE-2026-109619: PHP2Shell affected versions and fixes

Check which PHP versions fix PHP2Shell, what to confirm with your hosting provider and how to update your site safely.

Last verified: October 22, 2026. PHP has released fixes for CVE-2026-109618 and CVE-2026-109619, known together as PHP2Shell. These vulnerabilities affect PHP itself and can allow remote code execution (RCE) without authentication under specific conditions. Updating a plugin or seeing a working homepage is not evidence that PHP has been patched. Canadian Centre for Cyber Security alert.

Which PHP versions fix PHP2Shell?

Both vulnerabilities have a critical severity score of 9.2 under CVSS v4.0. The PHP project published the first fixed releases on October 21, 2026. In each branch below, earlier official releases are affected:

PHP branchFirst fixed release
PHP 8.28.2.35
PHP 8.38.3.36
PHP 8.48.4.27
PHP 8.58.5.12

Use the appropriate fixed release, or a later release in the same supported branch, after checking application compatibility. You do not need to move every application to PHP 8.5 to address these CVEs. PHP security announcement and release notices.

Vendor packages need a separate check. A distributor may apply the fix to an older version—a backport—without changing its base version number. Request the vendor advisory and complete package revision; do not classify a vendor-maintained package using this table alone.

PHP 8.1 and older no longer receive regular security updates from the PHP project. Some vendors provide backports. For these vulnerabilities, the PHP security team also made minimal source patches available for 7.4, 8.0 and 8.1. Those patches do not restore normal upstream support. Ask for an immediate remediation decision and a supported-version migration plan. CERT-EU recommendations.

Need help organizing the update? Discuss your PHP patching needs with OH Digital. Tell us your domain, platform and hosting provider. We can review your update requirements for Magento 2/Adobe Commerce, WordPress/WooCommerce or cloud environments and identify which steps require your hosting provider. Do not send passwords in the inquiry.

What should you do now?

  1. Identify every PHP environment. Include the main site, stores, subdomains, customer portals, test systems and third-party products that embed PHP.
  2. Confirm who is responsible for updating PHP. Your hosting provider, agency and application team may have different responsibilities.
  3. Patch exposed installations promptly. Internet-facing systems accepting untrusted requests deserve immediate attention, even if they do not process payments.
  4. Verify the active environment. Confirm the fixed package is running across the relevant workers, replicas and deployed containers.
  5. Test critical business workflows. Check orders, payments, forms and integrations as applicable; a successful homepage request is insufficient.

PHP identifies installations running affected versions and serving web requests as at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. Exploitability varies by configuration. PHP’s affected-environment guidance.

How the two vulnerabilities differ

CVE-2026-109618: out-of-memory corruption

An allocation failure can interrupt PHP while internal request data is only partly initialized. Request cleanup can then act on invalid state. Remote code execution was validated with mod_php before application code executes.

PHP-FPM terminates a worker process if request startup fails, preventing that particular attack sequence. However, out-of-memory errors triggered through application code after startup may still expose FPM to this flaw. As of this review, the advisory reports no complete FPM exploit for this CVE. PHP advisory: RCE via OOM corruption.

CVE-2026-109619: stale state across requests

A worker can retain references to memory owned by a completed request. A later request on that worker can consume the stale state before normal initialization resets it. Exploitation requires both a reachable operation that leaves state behind and a later operation that consumes it.

The advisory reports validated RCE involving session handling in both mod_php and PHP-FPM. The FPM case depends on an application operation that creates the necessary conditions. Using FPM is therefore not a reason to skip remediation. PHP advisory: RCE via stale global state.

How to patch without losing track of the business

Agree on the scope before starting: affected domains, technical owner, hosting contact, target package or image, recovery point and acceptance checks.

  • Prepare recovery. Verify backups cover the required files, database and configuration. Decide how orders or registrations created during maintenance would be reconciled.
  • Check compatibility. Use the appropriate fix for your platform. Keep an unrelated redesign or platform migration outside the urgent change.
  • Replace running components. For customer-built containers, rebuild with patched PHP and redeploy the running services; changing an image without replacing instances is insufficient. Google Cloud’s PHP deployment guidance.
  • Verify remediation and functionality separately. Record the active package revision for each environment, then test the workflows that generate orders or leads. A command-line PHP version alone does not establish which runtime handles web requests.
  • Close with evidence. Keep the covered assets, applied fix, test results, remaining exceptions, owners and deadlines in one handover.

For stores, test the cart, an authorized purchase, payment confirmation, order recording, tax and shipping rules, and any connected enterprise resource planning (ERP) or logistics systems. For service businesses, include form submission, notification and arrival of the lead in the sales system.

If an update causes a compatibility failure, use the agreed recovery procedure while controlling exposure. Restoring a known vulnerable runtime must not be treated as completed remediation or a reason to reopen public access without safeguards.

What if you cannot patch immediately?

A PHP release or vendor package containing both complete fixes is the definitive remedy. If patching is not immediately feasible, consider isolating affected internet-facing applications from public networks until the fix is applied and verified. CERT-EU containment guidance.

For CVE-2026-109619, PHP documents the following limited configuration measures. Ask your server administrator to assess and apply them:

  • Set session.upload_progress.enabled=0 administratively before request parsing, using php.ini, an FPM pool or appropriate server configuration. Restart every worker. Do not rely on application ini_set() or FPM .user.ini for this early path.
  • On PHP 8.5, set fatal_error_backtraces=0 administratively and restart every worker. This addresses the confirmed fatal-backtrace path only.

Neither setting covers all stale-state variants. PHP’s configuration guidance.

For CVE-2026-109618, memory and request-limit changes require an infrastructure assessment. Removing PHP’s memory limit can affect service availability and does not prevent every allocation failure. Ask the responsible engineer to evaluate the full OOM advisory.

Firewall rules can provide additional protection during patching, subject to their inspection limits. They are not proof that PHP has been fixed. Test legitimate uploads, forms and integrations after changes. Google Cloud’s defense-in-depth guidance.

A message you can send your hosting provider

Please confirm our exposure to CVE-2026-109618 and CVE-2026-109619. Which domains and environments were checked? What complete PHP package or image revision contains the fix, and which vendor advisory confirms it? Is it active across all relevant workers and replicas? What remains our responsibility, and when will you provide final verification?

Even with managed hosting, confirm exactly what the provider covers. Ask whether secondary sites and customer-managed containers are included.

Does a vulnerable version mean the site was compromised?

No. A vulnerable component requires remediation, but it does not by itself prove exploitation. Equally, installing a patch does not establish that the environment was never compromised.

If you find unexplained activity, preserve relevant logs and evidence and arrange specialist investigation. Do not run untrusted exploitation tools against production. PHP warns that an absence of relevant log entries is not proof of safety. PHP’s logging and audit limitations.

Frequently asked questions

Is updating WordPress, Magento or plugins enough?

No. Application or plugin updates do not confirm that the PHP runtime contains these fixes. Verify PHP separately, then check application and extension compatibility. These vulnerabilities are in PHP, rather than a specific content management system or store platform.

Can the Magento version checker confirm these fixes?

No. It checks the Magento application version. PHP runtime remediation must be confirmed by the responsible technical team or hosting provider.

Do I need to change hosting providers?

Start by requesting a verifiable response and dates. If the provider cannot supply them, evaluate alternatives through a controlled migration plan rather than an improvised move.

What should I include when asking OH Digital for help?

Your domain, platform, hosting provider, technical contact and critical workflows. Mention whether you need help with a Magento 2/Adobe Commerce application, WordPress/WooCommerce site or cloud environment. We will agree on the scope and provider responsibilities before scheduling work.

Request help planning your PHP security update. Let’s establish what needs updating, who owns each step and how you will verify the result.