Skip to main content
All incident reports
Incident report

PHP2Shell: critical PHP flaws reach Siemens industrial and energy products

Two critical remote code execution flaws in the PHP runtime, disclosed on 21 October 2026 and named PHP2Shell, have reached Siemens industrial, building and energy products. Siemens has published advisories for the affected products, several of which have no fix, and PHP has since issued further patches for related flaws.

· First published

The short version

  • The flaws. CVE-2026-109618 and CVE-2026-109619 are critical, unauthenticated remote code execution (RCE) flaws in the core PHP language runtime, together called PHP2Shell. The PHP project and security researchers disclosed them on 21 October 2026.
  • Where they landed. Siemens ProductCERT advisories republished by CISA on 12 November list RUGGEDCOM APE1808, which runs Palo Alto Networks PAN-OS, and a range of building automation and energy products as affected. Several of those products have no fix available.
  • Exploitation. SecurityWeek describes CVE-2026-109619 as now widely exploited. No source gives the scale of that exploitation or names the attackers.
  • New patches. On 19 November PHP released 8.6.0 and 8.5.13 with fixes for seven critical RCE flaws, two of which concern CVE-2026-109619, plus 10 high and medium-severity issues. Patches for most issues are also in older supported branches.
  • Exposure advice. CISA recommends keeping control-system devices off the internet, placing them behind firewalls and away from business networks, and using a maintained VPN for remote access where it is required; Siemens recommends protecting network access to devices with appropriate mechanisms.

Timeline

DateEvent
21 OctoberThe PHP project and security researchers disclose two critical, unauthenticated RCE flaws in the PHP runtime, CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell.
OctoberCVE-2026-115560, a flaw in PHP's session upload progress feature, is publicly disclosed two days after the PHP2Shell patches, according to SecurityWeek.
23 OctoberSiemens ProductCERT publishes the initial version of its advisory on RUGGEDCOM APE1808.
28 OctoberSiemens revises the RUGGEDCOM advisory to add PAN-OS to the remediation.
12 NovemberCISA republishes the Siemens ProductCERT advisories covering RUGGEDCOM APE1808 and the affected building automation and energy products.
19 NovemberPHP releases 8.6.0 and 8.5.13 with fixes for seven critical RCE flaws and 10 high and medium-severity issues.

What the PHP2Shell flaws are

Both flaws sit in the PHP runtime and are classed as use-after-free weaknesses, where a program keeps using memory after releasing it. CVE-2026-109618 arises when PHP handles an out-of-memory error and leaves request memory uninitialised; CVE-2026-109619 occurs when PHP's global state still refers to request memory that has already been freed. Siemens says both can lead to remote code execution without authentication. For RUGGEDCOM APE1808 it rates CVE-2026-109618 at CVSS 9.8 and CVE-2026-109619 at 8.1.

The flaws matter beyond web servers because PHP is embedded in appliances. Siemens' building automation and energy advisory says the company is still assessing its portfolio and that its findings may change. It has released new versions for some products, is preparing further fixes, and recommends mitigations where no fix exists.

Which products are affected

On RUGGEDCOM APE1808 the exposure comes through Palo Alto Networks PAN-OS. Siemens lists PAN-OS 10.2, 11.1, 11.2, 12.1 and 12.2 on the device as affected and directs customers to the corresponding PAN-OS upgrade, obtained through customer support.

The second advisory covers AMIS TS, blueplanet 360 NX3 M6 variants, Energy Engage V2.0SP9 and V3.1SP1, Local Monitoring bt-monitoring-vm, Spectrum Power 3, 4, 7 and TG, and Heliox Rapid. Fixes exist for some entries, such as Energy Engage V3.1SP1 and Local Monitoring bt-monitoring-vm. Siemens lists no fix as available for AMIS TS, the blueplanet units and several Spectrum Power 4 components, and no fix planned for Energy Engage V2.0SP9.

The November patches

PHP's 19 November release addresses seven critical RCE flaws. SecurityWeek reports that CVE-2026-129481 is an incomplete fix for CVE-2026-109619 and that CVE-2026-129182 covers additional exploitation scenarios for the same flaw. PHP says code execution through those specific paths has not been demonstrated, and that PHP 8.2 is not affected by CVE-2026-129481.

The batch also covers session upload progress, session deserialisation, a timezone cache use-after-free, and a PHP-FPM request smuggling bug in which unread bytes from one request can be treated as a second request on a reused connection, bypassing front-end routing. PHP says a suitable gadget chain — existing application code an attacker can string together — is needed for some of the deserialisation paths.

What is not known yet

  • No source names the attackers exploiting the PHP2Shell flaws or states how many organisations have been affected.
  • No source says whether any Siemens customer or PAN-OS deployment has been compromised through these flaws.
  • Whether Siemens will issue fixes for the products it currently lists as having none, and on what timetable.
  • Whether any of the flaws patched on 19 November have been exploited in the wild.
  • How many PHP deployments, embedded in appliances or otherwise, have applied the October PHP2Shell patches.

What to do

If you run Siemens products

  1. Check your inventory against the two Siemens ProductCERT advisories republished by CISA on 12 November; Siemens says its assessment is still changing.
  2. Apply the vendor fixes Siemens lists where they exist, and obtain the PAN-OS upgrade for RUGGEDCOM APE1808 through Siemens customer support.
  3. For products with no fix, apply the mitigations in the advisory and ask Siemens ProductCERT for a status update.
  4. Keep control-system devices and remote devices off the internet and behind firewalls, separated from business networks.

If you run PHP

  1. Upgrade to a fixed release listed in PHP's advisory, such as PHP 8.6.0.
  2. Confirm which of the new CVE identifiers apply to your version before assuming a single upgrade covers them; PHP says 8.2 is unaffected by CVE-2026-129481.
  3. Review code paths that unserialise session data, since several of the new flaws need a reachable gadget chain to reach code execution.

For everyone else

  1. Track runtimes bundled inside third-party appliances, not only servers you patch yourself, and subscribe to both the upstream runtime advisories and the appliance vendor's notices.
  2. Where remote access to operational equipment is needed, use a VPN and keep the VPN software itself current.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

We email you about this topic only; unsubscribe any time. See our Privacy Policy.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.