PHP2Shell

Unauthenticated code execution through PHP request lifecycle flaws

Published Oct 21, 2026 2 related CVEs 1 vendor 1 product

Overview

PHP2Shell names the two PHP runtime vulnerabilities CVE-2026-109618 and CVE-2026-109619, disclosed with the October 21, 2026 security releases. They can allow an unauthenticated attacker to corrupt memory and execute code in a web-serving PHP process.

CVE-2026-109618 concerns cleanup of partially initialized data after an out-of-memory interruption. CVE-2026-109619 concerns request-owned state that outlives its backing memory and may be reused by a later request in the same worker. Exploitability varies by PHP version, server API, configuration and reachable code paths; Apache mod_php is especially exposed because demonstrated attacks can run before application code.

The PHP team identifies web-serving installations using PHP-FPM, mod_php, php-cgi, FrankenPHP and LiteSpeed as at risk. This is a runtime problem that can affect otherwise updated applications. The original fixes shipped in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, with distribution backports available separately.

On October 23, PHP also described a separate session-upload-progress issue, CVE-2026-115560, requiring an unusual runtime change of the session serializer. It is not one of the two original PHP2Shell CVEs listed here. Review that follow-up advisory too: disabling upload progress blocks the documented session paths but is not a complete substitute for fixing the original runtime vulnerabilities.

Affected Technologies

Vendors
Php
Products
Php

Get vulnerability alerts

Follow the technologies you use and get notified about new vulnerabilities and updates to existing CVEs.

Start monitoring