English edition · cyberattaques.org in FrenchFrançais
VulnerabilityPatch available

PHP fixes two critical remote code execution flaws as a third remains unpatched

On 21 October 2026, the PHP project released versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35, fixing two vulnerabilities that allow unauthenticated remote code execution. A third flaw disclosed on 23 October has only a mitigation so far, and every PHP installation serving web requests is affected, along with many products that embed PHP.

What to do now Illustration photo (programming code screen)
CVSS severity9.2Critical
EPSS probability100 %
ExploitationNot observed
PatchAvailable
Product
PHP
Affected versions
PHP 8.5 before 8.5.12, 8.4 before 8.4.27, 8.3 before 8.3.36, 8.2 before 8.2.35, and end-of-life branches (8.1 and older)
Fixed in
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35
CVE
CVE-2026-109618

CERT-EU updated its advisory 2026-018 on PHP on 23 October 2026. On 21 October, the PHP team shipped fixes for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Each lets an unauthenticated attacker run code remotely. Technical details are being discussed in public and early proofs of concept are circulating. CERT-EU says this makes active exploitation more likely.

CVE-2026-109618 sits in out-of-memory handling. When a request exceeds the memory_limit setting, PHP aborts it abruptly. That abort can land while internal request data is only half initialised, for instance during parsing of a form-based file upload. Request cleanup may then free memory that was never initialised and that can still hold attacker-controlled data from earlier allocations.

CVE-2026-109619 involves stale global state. Internal state tied to one request can outlive the memory backing it, for example after a fatal error. A later request handled by the same worker may then use that state before normal initialisation resets it. A demonstrated exploit shows that a single unauthenticated request can trigger the attack before any application code runs.

Every installation that serves web requests is exposed, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. The PHP team rates mod_php as the riskiest setup. End-of-life branches (8.1 and older) are also affected, and minimal source backports have been published for PHP 7.4, 8.0 and 8.1. Commercial and open-source software that embeds PHP may be vulnerable too. CERT-EU points to the NCSC-NL php2shell GitHub repository to help identify such products.

On 23 October, PHP disclosed a third remote code execution flaw, CVE-2026-115560. No technical details are available yet. It reportedly affects only unusually configured web applications, and PHP considers it an unlikely risk. No out-of-band release is planned, so the fix will come with the next regular release. Until then, disabling session.upload_progress.enabled is the advised protection.

Users of the volunteer-run rpms.remirepo.net repository did not receive updates on release day. The PHP team urges them to switch to distribution packages or build from source. Linux distributions and LTS vendors received the patches in advance.

Action plan

What to do now

  1. Update every PHP installation to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or to your distribution's patched packages.
  2. For PHP 8.1 and older, obtain a backport from your LTS vendor or move to a supported branch, and otherwise apply the PHP team's source backports for 7.4, 8.0 and 8.1.
  3. Set session.upload_progress.enabled=0 in php.ini or the FPM pool configuration and restart every worker, which covers CVE-2026-115560 and part of CVE-2026-109619.
  4. If you cannot patch immediately, isolate internet-facing PHP applications from public networks until the fix is applied and verified.
  5. Use the NCSC-NL php2shell repository to identify third-party products that embed PHP, and check with their vendors for updates.

Sources