Home › Vulnerabilities

Two Critical PHP Flaws: Update Now

Published October 21, 2026 · Last updated October 21, 2026

PHP CVE Critical Remote Code Execution RCE Memory Safety Unpatched Patch WordPress Drupal Magento Apache

What happened: On October 21, 2026, the PHP project put out emergency security updates for two critical flaws. PHP is the programming language behind a huge share of websites, including many built with WordPress, Drupal, and Magento. The flaws are tracked as CVE-2026-109618 and CVE-2026-109619. PHP rates both 9.2 out of 10 on the CVSS v4.0 severity scale, which counts as critical.

Why it matters

According to PHP's own advisory, both flaws can let an attacker run their own code on a web server without logging in. According to WIRED, researchers at Wiz say the bugs can also leak server memory that may hold passwords, login tokens, and API keys, and Cloudflare reported seeing early attacks. Some government websites in Europe went offline for a while as a safety step, according to WIRED and Reuters.

Who is at risk

PHP says every PHP setup that serves web requests is at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed. PHP says the risk is highest for Apache with mod_php. WIRED reports that the problem goes back as far as PHP 5 from 2004.

What the two flaws do

PHP's advisory describes them in plain terms. In CVE-2026-109618, running out of memory can interrupt PHP while internal request data is only partly set up, and the cleanup step may then treat that broken data as valid. In CVE-2026-109619, internal state that belongs to one request can survive after its memory has been freed, so a later request handled by the same worker may use that stale state. PHP says it has a demonstrated exploit for mod_php where a request from someone who never logged in can trigger the attack before any application code runs.

How fast attacks started

PHP gave advance notice on October 20, without technical details, and said both flaws scored 9.2, WIRED reports. According to WIRED, security firm Sansec predicted mass attacks within 15 minutes of the release, and the fixes came out just before 10 a.m. Eastern on October 21. Wiz, OpenAI, and security firm Calif each say they found the bugs, according to WIRED. Britain's National Cyber Security Centre told organizations to find systems running PHP, focus on internet-facing ones, and consider taking a system offline if it can't be fixed right away, WIRED reports.

What to do

  • Update PHP to 8.5.12, 8.4.27, 8.3.36, or 8.2.35. PHP says updating is the only complete fix.
  • Using a web host or a Linux distribution? Ask your host, or check your vendor for updated packages. PHP says vendors got the fixes early.
  • On PHP 8.1 or older? The PHP project no longer supports these versions. Move to a supported version, or ask your vendor about a backported fix. PHP also posted basic source patches for 7.4, 8.0, and 8.1.
  • Just a website visitor? You don't need to install anything. This is a server problem, not a problem on your phone or computer.
  • Think a server was hacked? According to WIRED, the FBI's cyber division advises you to isolate the system, save your web server and PHP logs, and report it to your local FBI field office.

If you can't update today

PHP lists stopgap settings, such as a lower post_max_size for sites that don't need large uploads and turning off session.upload_progress.enabled, then restarting every worker. PHP stresses that these steps reduce exposure to specific attack paths but do not make an installation safe. On October 23, PHP added an informational note about a separate, unlikely session issue, CVE-2026-115560, and suggested keeping session upload progress turned off until the next regular bugfix release.

Note: PHP 8.2 stops getting security fixes after December 31, 2026, so plan to move off it soon.

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.