Skip to content
Reporting obligations

PHP2Shell and the Cyber Resilience Act: what manufacturers must do now

6 min read

On 21 October 2026 the PHP project fixed two critical vulnerabilities in the PHP core, known as “PHP2Shell”. They allow attackers to execute code on the server without authentication. If you ship PHP in a product with digital elements, check now what the Cyber Resilience Act requires – the reporting obligation under Art. 14 has applied since 11 September 2026.

What is known (as of 23 Oct 2026)

  • CVE-2026-109618 (“RCE via OOM corruption”): when memory runs out, PHP aborts a request while internal request data is only partially initialised; request cleanup then treats the invalid data as valid.
  • CVE-2026-109619 (“RCE via stale global state”): request state survives after its memory has been freed. A later request handled by the same worker may use it before it is reset (use-after-free).
  • The PHP project rates both CVSS 4.0 9.2 (critical) and states that they can allow unauthenticated remote code execution.
  • Fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. According to the advisories, all earlier versions in these branches are affected.
  • According to the PHP project, all PHP installations serving web requests are at risk – PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed; it considers the risk highest for mod_php.

On 23 October 2026 the PHP project published a further notice (CVE-2026-115560): it suggests setting “session.upload_progress.enabled=0” until the next regular release. Only a specific session configuration is affected; the project calls the attack vector unlikely.

Source: PHP project: security advisory of 21 Oct 2026 · GHSA-w8hw-w9fx-j79w (CVE-2026-109618) · GHSA-6wmf-4rv5-p3rp (CVE-2026-109619) · PHP project: notice on session upload progress of 23 Oct 2026

Is it being actively exploited?

The security company watchTowr reports that its honeypot network has observed exploitation of both flaws since 21 October 2026; it does not publish further evidence. As of 23 Oct 2026, neither flaw is listed as exploited in CISA's Known Exploited Vulnerabilities catalogue or in the exploited vulnerabilities list of the European Vulnerability Database (EUVD). The EUVD lists them as EUVD-2026-107260 and EUVD-2026-107265.

Important under the Cyber Resilience Act: whether “PHP2Shell” is exploited somewhere on the internet does not by itself decide your reporting obligation. What matters is whether the vulnerability was exploited in your product – see the next section.

Source: watchTowr: PHP2Shell (21 Oct 2026) · CISA: Known Exploited Vulnerabilities Catalog · EUVD-2026-107260 · EUVD-2026-107265

Do I have to report?

Under Art. 71(2), Art. 14 CRA has applied since 11 September 2026 and, under Art. 69(3), also to products placed on the market before that date. You must report actively exploited vulnerabilities contained in your product with digital elements. Under Art. 3(42), a vulnerability is actively exploited if there is reliable evidence that a malicious actor has exploited it in a system without permission of the system owner.

For most manufacturers, PHP is a third-party component. According to the Commission guidelines (point 218), a vulnerability in a third-party component is only reportable if it is exploitable in your own product and has been exploited. This means:

  • Your product contains an affected PHP version, but there is no evidence of exploitation in your product: no mandatory notification under Art. 14. Voluntary reporting under Art. 15 is possible; however, according to its FAQ (No 27, as of 15 Oct 2026), ENISA's reporting platform does not yet accept voluntary notifications.
  • There is reliable evidence that the vulnerability was exploited in your product – for example on a device or installation at a customer: mandatory notification under Art. 14.

In the second case the deadlines run from the moment of awareness – according to the guidelines (point 213), the moment when, after an initial assessment, you have a reasonable degree of certainty that a reportable case exists: early warning within 24 hours, notification within 72 hours of becoming aware, final report no later than 14 days after a corrective or mitigating measure is available. Notifications go through ENISA's reporting platform to the competent CSIRT; in Germany this is CERT-Bund at the BSI.

Whether the deadline for the final report already starts with the PHP releases of 21 Oct 2026 or only with the update for your product is not expressly settled by the regulation or the guidelines. Record in the case from when you consider which measure available, and give your reasons.

After becoming aware, you must also inform the impacted users about the vulnerability and, where necessary, about measures they can take to mitigate its impact (Art. 14(8)).

Source: Art. 14(1), (2), (8) CRA · Art. 3(42) CRA · Art. 69(3) CRA · Art. 71(2) CRA · Art. 15 CRA · Commission guidance C/2026/6013, points 213, 218 · ENISA FAQ on the Single Reporting Platform, No 27

Which products may be affected

The Cyber Resilience Act covers products with digital elements – software and hardware including their remote data processing solutions (Art. 3(1) and (2)). Cloud services that do not support the functionality of such a product are not covered; according to Recital 12, SaaS offerings fall under the NIS 2 Directive. Typical cases where PHP is part of the product:

  • web interfaces of devices – routers, NAS, cameras, controllers, gateways – shipped with PHP;
  • software run by the customer (on-premises) that brings its own PHP runtime, for example as a container image or installation package;
  • appliances and virtual machines with their own web server and PHP.

If you only ship PHP code and the customer operates the PHP runtime, the vulnerable runtime is not part of your product. A notice to your customers is still sensible.

Source: Art. 3(1), (2) CRA · Recital 12 CRA · PHP project: security advisory of 21 Oct 2026

What also applies from 11 December 2027

The vulnerability handling requirements of Annex I, Part II and Art. 13 apply only from 11 December 2027. But they already describe how such a case should be handled today:

  • Identify and document vulnerabilities and components, including by means of an SBOM (Annex I, Part II, point 1).
  • Address and remediate vulnerabilities without delay in relation to the risks, including by providing security updates (point 2).
  • Once an update is available, publicly disclose information about the fixed vulnerability (point 4).
  • Disseminate security updates without delay and, as a rule, free of charge, with advisory messages on possible action (point 8).
  • Anyone who identifies a vulnerability in a component reports it to the person or entity manufacturing or maintaining it (Art. 13(6)) – for PHP2Shell this has already happened.

Source: Annex I, Part II, points 1, 2, 4, 8 CRA · Art. 13(6) CRA · Art. 71(2) CRA

What to do now

  1. Check exposure: which products and versions contain PHP, which version, which mode of operation (FPM, mod_php, CGI)? A current SBOM per version answers this in minutes – provided the PHP runtime is listed in it with its version.
  2. Update: to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, and provide a security update for your product. The PHP project calls updating the only complete remedy.
  3. Until then, review the interim measures in the advisories, such as “session.upload_progress.enabled=0” and, on PHP 8.5, “fatal_error_backtraces=0”, and restart all workers. According to the PHP project, these measures do not protect completely.
  4. Older branches: the PHP project has not announced new releases for versions before 8.2; PHP 8.2 receives no security fixes after 31 December 2026. Plan the migration and record the decision in the risk assessment.
  5. Take signs of exploitation at customers seriously: record the moment of awareness with the time and start the deadlines under Art. 14.
  6. Inform customers: which products and versions are affected, which update helps and what they can do until then.

The guide “Reporting obligations under Art. 14 CRA” explains step by step how a notification works; in the reporting drill you can walk through the process without signing up.

Source: GHSA-w8hw-w9fx-j79w (CVE-2026-109618) · GHSA-6wmf-4rv5-p3rp (CVE-2026-109619) · PHP project: PHP 8.2.35 and end of support for PHP 8.2

Related guides

Terms in the Cyber Resilience Act glossary

Sources

Status of the Commission guidance: the Commission approved its content on 27 July 2026 (C(2026) 5252). On 17 November 2026 the guidance was published in the Official Journal as Communication C/2026/6013, in all official languages. According to our comparison, the point numbers have not changed. The guidance is not binding, but it shows how the Commission reads the Regulation (as of 11/2026).

First published 23 Oct 2026, last updated 23 Oct 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.