When a critical CVE lands in a library, the first hours of a response go into working out which applications pull it in. PHP2Shell skips that step. Both flaws sit in the PHP engine, so the only facts that matter are which interpreter builds you run, how each one serves traffic, and whether its version is above the fixed line. Those facts are already written down in an SBOM generated by Anchore Enterprise.

PHP2Shell at a glance

CVE IDsCVE-2026-109618, CVE-2026-109619
Severity9.2 (CVSS v4.0, PHP security team); 9.8 (CVSS v3.1, NVD)
Fixed releases8.5.12, 8.4.27, 8.3.36, 8.2.35, published October 21, 2026
End-of-life branches5.4 through 8.1 receive no upstream release
Exploitation (as of October 26)Attempts reported by watchTowr and Amazon; Working shells confirmed on honeypots (October 24); not yet listed in CISA KEV

Wiz Research disclosed the flaws alongside the PHP project’s security releases. Both are memory-safety bugs that surface when PHP hits a fatal error, such as exhausting its memory limit, partway through handling a request. Wiz chained them into unauthenticated code execution against the official WordPress, Drupal and Joomla container images, and points out that the application on top doesn’t need a bug of its own for the server to be at risk. The PHP project’s release notes are blunt about mitigation: no workaround is complete, and updating is the only safe option.

Attackers moved early. watchTowr reports exploitation attempts against both CVEs in its honeypot network since October 21, and Amazon has reported an attempt dated October 17, four days before the fix was available. CISA had not observed exploitation as of its October 21 alert. When KEV status, vendor packages and exploit availability are all changing by the hour, the teams that respond well are the ones that can re-ask “where are we exposed?” as often as the facts change.

What Anchore Enterprise sees inside a PHP image

Composer files describe the libraries a PHP application uses. The interpreter comes from somewhere else, and frequently from a source build that no package manager ever recorded: the official PHP: images on Docker Hub compile PHP during the image build, and a large share of WordPress, Drupal and in-house images use them as a base.

Anchore Enterprise includes a dedicated PHP interpreter cataloger for this case. Instead of relying on a package database, it inspects the binaries in the image and reads the version string compiled into each one. It records three kinds of interpreters, which correspond to the common ways PHP is deployed:

  • php-cli: the php command-line binary
  • php-fpm: the FastCGI process manager typically paired with Nginx
  • libphp: the Apache module, often called mod_php

Each is recorded with the package type binary, along with any compiled C extensions found alongside it. PHP installed from a distribution repository keeps its distro package name, such as php8.3-fpm on Debian or Ubuntu, and Anchore Enterprise evaluates it against that distribution’s own advisories. Debian, Red Hat and Ubuntu have already published fixed packages, so those matches reflect distro fixes rather than upstream version numbers alone.

To check any given image, analyze it and list its binary content and PHP2Shell findings with AnchoreCTL. This example greps for both PHP vulnerabilities in question.

image='docker.io/library/php:8.3-fpm'
vuln='CVE-2026-10961[89]'
anchorectl image add --wait $image
anchorectl image content $image -t binary
anchorectl image vulnerabilities $image -t all | grep -E $vuln

Querying your fleet for PHP2Shell

Anchore Enterprise stores an SBOM for every image it analyzes, so answering PHP2Shell across a fleet doesn’t start with a rescan. The questions run against inventory that existed before anyone had heard the name.

Start with a feed check. Confirm the “DATA SERVICE BUILD TIME” is recent before relying on any match:

anchorectl feed list
FEEDGROUPENABLEDDATA SERVICE BUILD TIMERECORD COUNT
Vulnerabilitiesalpine:3.10true2026-10-23T12:15:02Z2363
Vulnerabilitiesdebiantrue2026-10-23T12:14:56Z7925
Vulnerabilitiesrhel:10true2026-10-23T12:15:32Z19278
……………

The Anchore Enterprise UI offers a vulnerability search feature that will inform you what asset(s) are affected by a particular vulnerability. So search for a PHP vulnerability to find out if you’re impacted.

The result shows what is currently impacted across your fleet of applications:

And because the SBOM for all application assets is already stored, this information becomes available as soon as the vulnerability feeds update. There’s no need to reassess the images, the SBOM itself is sufficient. 

If you prefer to query via the API for the same information, check the zero-day quickstart guide for steps.

When the tag moves but the pod doesn’t

PHP2Shell has a wrinkle that catches teams who track images by tag. As maintainers republish base images on the fixed releases, a tag like php:8.3-fpm starts pointing at a new digest. Every pod that started before the rebuild keeps running the old one under the same name, and a registry view will happily report the tag as fixed.

Anchore’s Kubernetes inventory agent tracks running workloads by digest, so it shows which pods are still on a vulnerable build after the tag has moved on. Join that inventory with the package search above and the output is a list of live workloads to restart or redeploy, not a list of images sitting in a registry.

To keep fresh builds from reintroducing the problem, add a rule in Anchore Enterprise that fails any image matching either CVE ID, and leave it in place until your oldest PHP builds are migrated. Those need a plan of their own. According to AWS’s security bulletin, branches 5.4 through 8.1 get no upstream fix, and on those branches CVE-2026-109618 can’t be fixed at all. The by-package query is the quickest way to find out how many of them you still run.

The outcome: a PHP2Shell answer from data you already hold

Go back to where this started. PHP2Shell is a version question about an interpreter, and that interpreter is often invisible to tools that read application manifests. Answering it in hours depends on having recorded every PHP build, by name, version and digest, before the CVE had a number.

The technical outcome is a precise list: which images contain php-cli, php-fpm or libphp below the fixed releases, and which running pods still use them. The business outcome is being able to tell leadership and customers where you stand while exploitation is still ramping up, then showing that list getting shorter as rebuilds roll out.

We’ve seen this pattern before. During Log4j, an Anchore Enterprise customer that already stored its infrastructure as SBOMs answered the exposure question with a single query, as described in our webinar on zero-day response. Our zero-day quickstart covers both query methods, scoping and scheduled reports.

If you’d like to see how long PHP2Shell would take to answer in your own environment, request a demo and bring the list of PHP images you know about. We’ll help you find the ones you don’t.