PHP SECURITY & UPGRADES PHP2Shell: Fixing CVE-2026-109618 and CVE-2026-109619 in Business Websites

PHP application servers protected by a security shield after a runtime update

By NSDIT

Guidance checked: 17 November 2026. PHP2Shell refers to two critical PHP runtime vulnerabilities, CVE-2026-109618 and CVE-2026-109619. They can permit unauthenticated remote code execution under relevant conditions. Businesses running PHP websites should prioritise a runtime update, including when the application uses Laravel, Symfony, WordPress or another PHP platform. Check the linked vendor guidance for subsequent updates.

What are the two vulnerabilities?

CVE-2026-109618 concerns memory corruption during out-of-memory handling. CVE-2026-109619 concerns request state that can retain references to freed memory. These are interpreter issues: changing an application dependency or adding a framework validation rule is not a replacement for patching PHP itself.

The PHP project identifies web-serving installations including mod_php, PHP-FPM, CGI, FrankenPHP and LiteSpeed as requiring attention. Exposure varies by deployment; switching away from mod_php alone is not a remediation plan. See the PHP security announcement and the two official advisories below.

Which upstream versions contain the initial fixes?

Initial upstream fix releases for both CVEs; these are minimum branch-specific patch levels, not a recommendation to stop updating.
PHP branchAffected upstream releasesInitial patched release
8.28.2 releases before 8.2.358.2.35
8.38.3 releases before 8.3.368.3.36
8.48.4 releases before 8.4.278.4.27
8.58.5 releases before 8.5.128.5.12

Install the current appropriate vendor-supported security package. Linux distributions and hosting vendors may backport fixes without changing the apparent upstream version: confirm the package advisory and build revision. PHP 8.1 and earlier no longer receive normal upstream updates; obtain explicit vendor patch evidence or plan a supported-version migration.

A practical remediation checklist

  1. Inventory deployments. Include production, staging, scheduled jobs, container images and each web node. Ask your host which runtime actually serves each domain.
  2. Check runtime evidence. On a server you administer, php -v and php --ini identify the CLI binary and configuration. The web runtime can differ: verify FPM, Apache or your managed platform separately. Do not leave a public phpinfo() page online.
  3. Prepare the change. Confirm backups and restore procedures, test application compatibility and agree a deployment window. Use the operating-system, hosting or appliance vendor’s update procedure rather than a generic command copied for a different environment.
  4. Deploy everywhere. Update the relevant PHP packages. For containers, rebuild from a patched runtime image and redeploy; updating the host alone does not update PHP inside an image.
  5. Replace running processes. Restart or replace all affected PHP workers using the platform’s supported procedure. Confirm every node is running the intended patched build and effective configuration.
  6. Check business functions. Test logins, sessions, uploads, checkout, integrations and background jobs. Record the deployed package revision, test results and any follow-up work.

Do not miss the session upload progress follow-up

PHP’s 23 October advisory describes a separate, unusual session-serializer combination, tracked as CVE-2026-115560. It recommends disabling session upload progress pending the relevant follow-up release. Review that advisory against your current package before assuming the initial patches cover this additional issue.

; Startup configuration, where applicable under vendor guidance
session.upload_progress.enabled = 0

Apply this through the effective startup configuration and restart workers; an application-level ini_set() is too late for early request parsing. Check whether your application depends on the feature. This setting does not fix every PHP2Shell path.

What if you cannot patch immediately?

Coordinate temporary exposure reduction with your hosting or security team. The official advisories describe configuration-specific mitigations, but none is a complete substitute for updating. Do not casually set unlimited PHP memory: the OOM workaround has availability implications and requires carefully designed resource boundaries. A WAF, hidden errors or clean logs alone do not prove safety.

If you suspect the server was compromised

Patching does not remove an existing compromise. Preserve relevant logs and evidence, involve incident-response support and assess containment, recovery and credential rotation separately. Avoid running public exploit scripts against a live business site as a patch check.

How NSDIT can help your business

We can discuss a scoped PHP runtime and compatibility review, upgrade planning and deployment verification for businesses across the UK, Europe and USA. Explore our PHP development and maintenance services or legacy PHP modernisation checklist. Request a PHP upgrade discussion with your hosting platform and known runtime version; do not submit passwords or confidential logs.

Official references

Tell Us About Your Idea About Us Reliable and Trusted By Many

We've been in the business long enough to generate some good reviews. Yes! Who doesn't love their clients' positive feedback? We most definitely do. Wait! Here are some of the best ones.

Dealing with NSD IT is one of the best experience I have had with any professional since I started my business. They listen and deliver exactly what I ask for and more. They were very responsive and punctual throughout the entire process.

Pravin PatelAccounting solution

I have worked with NSD IT for four years with design, defining project concepts and business rules. They have very skilled people, and NSD IT has given the project an extra boost and value that I warmly recommend to anyone.

Abbas KananiC Click Ltd

NSD IT will take care of you, they will prioritize customer satisfaction at all cost and will provide the best work and updates they can. Not to mention they also work in a very timely manner.

Alex Cloud IT Limited

Fully satisfied with the quick response time, in-house knowledge, communication and flexibility to scale up resources when needed. Feels like they work nearby.

John Cosmic Healthcare Limited

Ready To Talk?

One day your plans will come to life, and you'll be exactly where you wanted to be. But for that, you need to take your very first step, why can't that be 'today'?

Interested ?

Yes! Let’s Talk