← All posts
Security

PHP2Shell Is Now Officially Exploited. Your First Hour as a Manufacturer.

On 26 October, CISA (the US cybersecurity agency) added both PHP2Shell flaws to its KEV catalogue. KEV stands for Known Exploited Vulnerabilities. A week earlier, CISA had said it had not yet seen successful exploitation. Now it counts both as actively exploited.

If you read our first write-up on 22 October, this is the update.

What happened, in order

  • 17 Oct: AWS sees exploit attempts, before any public disclosure.
  • 21 Oct: PHP ships patches: 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
  • 24 Oct: a researcher records 35 successful shell executions across three honeypots (decoy servers).
  • 26 Oct: KEV listing. US federal agencies have until 29 October to patch.

CVE-2026-109618 is a memory corruption bug in the PHP engine. CVE-2026-109619 is a stale request-state bug. A CVE (Common Vulnerabilities and Exposures) is a public ID for one flaw. Both score 9.2 on CVSS, a severity scale out of 10. An unauthenticated attacker can run code with crafted HTTP requests, and the vulnerable code goes back to PHP 5.4, from 2012. Delft University's lab counted more than 50,000 exploit requests from over 600 IP addresses.

Why a manufacturer cares

Since 11 September, the EU Cyber Resilience Act (CRA) asks manufacturers for an early warning within 24 hours of learning that a vulnerability in their product is being actively exploited. KEV is one signal, not the legal trigger. Whether you must report is a call for you and your counsel.

What is certain: since 26 October, this one is documented as exploited. If PHP serves pages inside your gateway, appliance or device interface, one question has to be answerable in minutes. Which release ships which PHP?

The first hour

The fixes map to branches:

Your branchFixed in
8.58.5.12
8.48.4.27
8.38.3.36
8.28.2.35

Look at how small the gap can be. A product on 8.2.34 is exactly one patch release from the fix, and 8.2.34 and 8.2.35 look the same to anyone who only knows "PHP 8.2". Older branches need an upgrade or a vendor-supported fix. Check php.net for what exists for yours.

The work is four steps:

  1. List every product and release that contains PHP.
  2. For each release, find the PHP and read its exact version.
  3. Compare it with the table above.
  4. Write down the decision and the date.

For a release tree that carries PHP source, steps 1 and 2 are two commands:

bomwerk scan . -o sbom.cdx.json
jq -r '.components[] | select(.name | test("php"))
       | [.name, (.version // "unknown"), .evidence.occurrences[0].location]
       | @tsv' sbom.cdx.json

grep '#define PHP_VERSION ' third_party/php-src/main/php_version.h

On a running device or container, php -v gives the same answer. Adjust the path to wherever your tree keeps the source.

Where bomwerk fits

The copy that gets missed is the vendored one: a PHP tree dropped into a repository for a web interface three years ago, with no manifest pointing at it. bomwerk scan walks a release tree and lists the vendored source it finds, PHP included, with its location. It writes one SBOM (Software Bill of Materials) per release in CycloneDX or SPDX, and the output is identical byte for byte on every run, so you can diff two releases. That turns "which release ships PHP?" into a lookup instead of an email thread.

Our paid extension, in preview, takes the next step: it registers what you shipped and drafts the CRA Article 14 report when a CVE lands.

PHP2Shell will not be the last one that asks this. The inventory is the part you build before the next listing, not after it.

Free repo scan: bomwerk.com

Not sure what your current SBOM is missing? We'll assess one repository across its supported ecosystems, explain the evidence gaps, and go deeper on C/C++ where the build context allows.

Get a free scan of one repo