What happened with PHP2Shell?
On October 21, 2026, the PHP project released 8.5.12, 8.4.27, 8.3.36 and 8.2.35 to fix two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619. In its security advisory, PHP says they "can allow unauthenticated remote code execution" and urges all users to update immediately. PHP's advance notice rated both CVSS v4.0 9.2.
CISA added both CVEs to its Known Exploited Vulnerabilities catalog on October 26, describing them as a PHP memory corruption vulnerability and a stale internal request-state vulnerability. On October 23, PHP also published an informational advisory suggesting session.upload_progress.enabled=0 until the next bugfix release, to close an unlikely related RCE vector.
Which PHP versions are affected?
- Fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released October 21, 2026.
- Anything older on those branches is affected.
- PHP 8.1 and older are end-of-life and get no fix. PHP says 8.2 reaches end of life on December 31, 2026.
How to check if you're affected
- Run
php -von servers and inside every running PHP container to see the exact version. - Search Dockerfiles for
FROM php:tags and provisioning code for PHP package installs. The runtime version doesn't appear incomposer.lock, so dependency scanners that only read lockfiles won't flag it. - List images in your registries and clusters built on PHP base images, including ones pinned to old minor tags.
- Check whether
session.upload_progress.enabledis on in yourphp.ini.
What to do now
- Upgrade to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 or later, then rebuild and redeploy affected images.
- Move anything on PHP 8.1 or older to a supported branch, and plan the move off 8.2 before December 31, 2026.
- Set
session.upload_progress.enabled=0until you're on the next PHP bugfix release, as PHP's October 23 advisory suggests.
Where Nullify fits
How Nullify Covers This Class of Attack
Nullify moves actively exploited vulnerabilities in the dependencies and images you use up the backlog as soon as they're disclosed, and prepares the version change as a pull request for each owner to review.
The vulnerable component is the PHP runtime in your images and servers, so the version lives in Dockerfiles and provisioning code, not in Composer files.
Frequently Asked Questions
What is PHP2Shell?
PHP2Shell is the name used for two critical vulnerabilities in the PHP interpreter, CVE-2026-109618 and CVE-2026-109619. PHP says they can allow unauthenticated remote code execution. Fixes shipped on October 21, 2026, and CISA lists both as exploited in the wild.
Which PHP versions fix PHP2Shell?
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released October 21, 2026. PHP 8.1 and older are end-of-life and get no fix, so they need to move to a supported branch.
Why didn't my dependency scanner flag PHP2Shell?
The vulnerable code is the PHP interpreter, not a Composer package. Its version is set by your base image or server packages, so scanners that only read composer.lock have nothing to match. Check php -v and your Dockerfiles instead.
Is PHP2Shell exploited in the wild?
Yes. CISA added CVE-2026-109618 and CVE-2026-109619 to its Known Exploited Vulnerabilities catalog on October 26, 2026, which means CISA has evidence of active exploitation. Treat any internet-facing PHP below the fixed versions as urgent.
Update Log
- Nov 17, 2026: page published from PHP's October 21 and 23 advisories and the CISA KEV catalog.