Block08 Security Audits Back to home

Security advisory

PHP2Shell attack help: CVE-2026-109618 and CVE-2026-109619

On 21 October 2026 the PHP project released emergency fixes for two critical remote code execution flaws, known together as PHP2Shell. Unauthenticated attackers can run code on unpatched PHP servers. Scanning and exploitation attempts are already widespread.

Published 2026-10-23. Updated 2026-10-23.

Who this attack hits

Every PHP install that serves web requests is in scope, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed. Apache mod_php is the highest-risk setup. WordPress, Laravel, Magento, Drupal, and many appliances embed PHP even when the product name does not say PHP.

Is block08.com affected?

block08.com is a static React site on GitHub Pages. It does not run PHP, so this site is not affected. If your product, store, or intranet runs PHP, you should treat this as urgent.

How Block08 can help

Block08 can help you find PHP across your estate, apply or verify the fixed versions, contain internet-facing systems that cannot be patched yet, and look for signs of compromise after the first exploit wave.

Get incident help

Fixed PHP versions

  • PHP 8.5.12
  • PHP 8.4.27
  • PHP 8.3.36
  • PHP 8.2.35
  • CVE-2026-109618: RCE via out-of-memory corruption
  • CVE-2026-109619: RCE via stale global state

What to do now

  1. 1. Inventory PHP

    List every internet-facing host that runs PHP, including images, PaaS platforms, and products that embed it.

  2. 2. Patch or isolate

    Update to a fixed PHP build. If you cannot patch yet, take the service off the public internet until you can.

  3. 3. Check for compromise

    Look for unexpected PHP workers, shells, new admin users, changed themes or plugins, and outbound callbacks.

  4. 4. Call incident help

    If you need a team to do this with you, Block08 can run the response and report what we find.

PHP2Shell questions

What is the PHP2Shell attack?

PHP2Shell is the name used for CVE-2026-109618 and CVE-2026-109619. Both bugs sit in PHP itself, not in one CMS plugin. A crafted request can lead to unauthenticated remote code execution on a vulnerable PHP worker.

Which PHP versions are safe?

Update to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35, or a later build on the same branch. PHP 8.1 and older have no official upstream release. Use a vendor backport or move to a supported branch.

Is Block08 or block08.com affected?

No. This website does not execute PHP. We published this advisory so operators who do run PHP can find help and a clear next step.

Can Block08 help us fix a PHP2Shell incident?

Yes. We can help with patching, containment, and a compromise review. Use the incident form or email security@block08.com.

Official sources