Critical PHP vulnerabilities: CVE-2026-109618 and CVE-2026-109619

On 21 October 2026, the PHP development team disclosed two critical vulnerabilities in the PHP runtime. Both can allow an unauthenticated attacker to execute code on a server that processes web requests with a vulnerable PHP release. The issues are sometimes referred to as PHP2Shell.

What the vulnerabilities affect

  • CVE-2026-109618: an out-of-memory handling flaw can leave request data only partially initialized before cleanup, creating a memory-corruption path.
  • CVE-2026-109619: request-owned internal state can remain after its backing memory is freed, allowing a later request handled by the same worker to use stale state.

Who needs to act

All PHP installations serving web requests should be checked, including Apache mod_php, PHP-FPM, CGI, FrankenPHP, and LiteSpeed deployments. The PHP project lists fixed releases as PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Older PHP versions require a security backport from the operating-system or long-term-support vendor, or an upgrade to a supported release.

Recommended response

  1. Update PHP through the operating-system or vendor package channel as soon as possible.
  2. Restart Apache, PHP-FPM, or other PHP workers after the update.
  3. Verify the version actually serving web requests, not only the command-line version.
  4. Review access and application logs for unusual requests or unexpected file changes.

Configuration workarounds and web-application firewalls may reduce some attack paths, but the PHP security advisory states that updating is the complete fix.

SILNAM has moved the website away from end-of-life PHP and is validating the vendor-fixed PHP release for this server. We will update this notice when the running web PHP version has been verified.

Read the official PHP security advisory and the NCSC guidance for current recommendations. This notice intentionally omits exploit instructions and access details.

Quick Navigation