Skip to content
RIZON
Back to Insights
CriticalVulnerabilities

PHP ships emergency fixes for two unauthenticated RCE flaws as EU bodies issue a joint patch call

Orizon TeamOctober 21, 20264 min readVulnerabilitiesPHP Group

On 21 October 2026 the PHP project released PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 to fix two vulnerabilities that let an unauthenticated attacker run code on the server: CVE-2026-109618 and CVE-2026-109619. The project's advance notice the day before rated both 9.2 under CVSS v4.0, and its GitHub advisories classify both as critical. According to PHP, every installation that serves web requests is affected, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. The risk is highest for mod_php, where PHP says a demonstrated exploit fires before any application code runs.

What the two flaws are

  • CVE-2026-109618, RCE via out-of-memory corruption (GHSA-w8hw-w9fx-j79w). An out-of-memory error can stop PHP while internal request data is only partly initialised, and request cleanup then treats that data as valid. The advisory says crafted multipart requests can trigger this within normal PHP limits. It reports a validated unauthenticated RCE over HTTP against mod_php with default settings and says a complete FPM exploit has not been demonstrated.
  • CVE-2026-109619, RCE via stale global state (GHSA-6wmf-4rv5-p3rp). In persistent workers, state owned by one request can outlive the memory behind it, and a later request on the same worker can use it before initialisation resets it. The confirmed paths are the session upload progress lifecycle, validated against mod_php and PHP-FPM, and the PHP 8.5 fatal-error backtrace path.

The PHP project no longer supports PHP 8.1 and older. It has published minimal backport branches for 7.4, 8.0 and 8.1, and notes that PHP 8.2 reaches end of life on 31 December 2026.

Exploitation status

On the day of release, neither the PHP advisories nor the EU joint statement reported exploitation in the wild. The GitHub advisories described validated exploits but no observed attacks. That changed on 26 October 2026, when CISA added both CVEs to its Known Exploited Vulnerabilities (KEV) catalog. KEV listing means CISA has reliable evidence of exploitation in the wild. CISA set a federal remediation due date of 29 October 2026 and marked both entries for forensic triage. In its php2shell repository, the Dutch NCSC links to third-party observations of exploitation but does not confirm active exploitation itself.

The EU response

On the same day, the European Commission (DG CNECT), ENISA, CERT-EU, Europol EC3 and the CSIRTs Network issued a joint statement asking organisations to act immediately. They asked organisations to:

  • identify PHP-based applications and coordinate with hosting and service providers;
  • apply the updates, starting with internet-facing systems;
  • isolate exposed applications from public networks where patching cannot happen immediately.

The statement also warns that many commercial and open-source products run PHP internally and may be affected even when this is not obvious. It points to the NCSC-NL php2shell repository, which tracks vendor status for products with a PHP dependency.

Why it matters for EU organisations

  • NIS2. Directive (EU) 2022/2555, Article 21(2) lists vulnerability handling (point e) and supply chain security (point d) among the required risk-management measures. Unauthenticated RCE in a common web runtime, including PHP hidden inside appliances and vendor products, falls under both. If a compromise turns into a significant incident, the 24-hour early warning and 72-hour notification deadlines apply.
  • DORA. Financial entities must treat this under their ICT risk-management framework and their ICT third-party risk oversight. That includes asking hosting providers and software vendors when their PHP components will be patched.
  • GDPR. Code execution on a web server that handles personal data is a security-of-processing issue under Article 32. A confirmed breach starts the Article 33 clock: notify the supervisory authority without undue delay and, where feasible, within 72 hours.
  • CRA. The joint statement notes that since 11 September 2026, manufacturers must report actively exploited vulnerabilities in their products through the CRA single reporting platform under Regulation (EU) 2024/2847. Vendors that ship PHP inside their products should check whether that duty applies.

What to do now

  • Patch to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, starting with internet-facing systems, and restart every PHP worker. If you run PHP 8.6.0 test builds, move to RC4 or a later release candidate; PHP says RC4 contains the fixes. Plan to move off 8.1 and older, and off 8.2 before its end of life on 31 December 2026.
  • Find the PHP you didn't know you had. Check appliances and vendor products against the NCSC-NL php2shell list, and ask hosting and SaaS providers to confirm their patch status in writing.
  • If you cannot patch immediately, isolate the system from public networks, as the EU statement advises. PHP's interim settings include memory_limit=-1, a low post_max_size, session.upload_progress.enabled=0 and, on 8.5 only, fatal_error_backtraces=0, with all workers restarted. PHP states that these settings do not make an installation safe.
  • Assume earlier compromise on unpatched exposed hosts. CISA advises watching for PHP worker processes that spawn shells or download tools. Review web-server and EDR telemetry from 21 October onwards.

Sources

VulnerabilitiesPHPRemote Code ExecutionCVE-2026-109618CVE-2026-109619Patch ManagementNIS2CRAENISA