Attacks reportedCVE published · 21 Oct 2026
PHP
CVE-2026-109618 Severity · Critical
CVSS 9.2
Affected
PHP 7.3.0 to 8.1, 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27, 8.5 before 8.5.12
Fixed in
PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12

CVE alert · PHP, CMS and e-commerce

CVE-2026-109618: a memory bug in PHP can let an attacker with no login run code on your web server

An attacker with no login can run their own code on servers with PHP 8.2 to 8.5 before the fixed releases, or with an older branch. Update today, then restart your web server and PHP services so the fix loads.

Check your systems with your AI agent

Paste this prompt into an AI agent that can run commands on your machines. It only reads versions and settings, asks before using administrator rights, and ends with a report.

Check whether my systems are affected by CVE-2026-109618 in PHP, then write me a report.

Read the alert first: https://securityaudit.ae/cve/cve-2026-109618-php/

What the alert says (facts checked 23 October 2026):
- Affected: PHP 7.3.0 to 8.1, 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27, 8.5 before 8.5.12
- Fixed in: PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12
- Exploited: Yes: Cloudflare saw attack attempts on 21 October 2026; no confirmed compromise; not in CISA's KEV catalog on 23 October 2026

Rules:
- Read only. Do not install, update, restart, delete or change anything, and never run exploit or proof-of-concept code.
- Run only commands that read versions or settings. Ask me before any command that needs sudo or administrator rights.
- If you do not know which machines, containers, cloud accounts or sites are in scope, ask me for the list before you start.
- If a machine cannot be reached or a command fails, say so. Do not guess.

Steps:
1. Find where PHP runs: servers, containers and their hosts, cloud services, sites.
2. On each one, read the installed version and the settings the alert names. The alert gives these commands:

    php -v

    <?php echo phpversion(), ' ', php_sapi_name();

    zgrep CVE-2026-109618 /usr/share/doc/php8.3-common/changelog.Debian.gz

    rpm -q --changelog php-common | grep CVE-2026-109618

3. Compare each version with the affected and fixed versions above. When a vendor or a distribution ships its own fixed package, the alert names it.
4. Report: one line per machine or service with the version found, Affected, Not affected or Unknown, and the evidence (the command and its output). Then the actions to take, in order, from the alert's "How to fix" section, and what you could not check.

Key facts

FactDetail
ProductPHP (language runtime)
Affected versionsPHP 7.3.0 to 8.1, 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27, 8.5 before 8.5.12
Fixed inPHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12
Severity9.2 Critical (CVSS 4.0, PHP Group); 9.8 Critical (CVSS 3.1, NVD)
Who can attackAny remote attacker who can send HTTP requests to the site; no login needed
ExploitedYes: Cloudflare saw attack attempts on 21 October 2026; no confirmed compromise; not in CISA's KEV catalog on 23 October 2026
CVE published21 October 2026

What an attacker can do

PHP is the program that runs the code behind WordPress, Drupal, Magento, Laravel and many in-house applications. CVE-2026-109618 is a memory corruption bug in this program. When a request hits the memory limit, PHP stops the request while some memory is only half set up. The cleanup step then reads that broken memory.

An attacker can use this bug to run their own code on your server. That code runs with the rights of the system account PHP uses. The attacker can then read or change anything that account can reach. If that account can open your database and site files, the attacker can read customer data and change pages or payment settings. The flaw is in PHP itself, so it can expose a site whose own code has no bug.

Who is affected

The PHP Group lists 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27 and 8.5 before 8.5.12. NVD, the US National Vulnerability Database, starts its range at 7.3.0. Older branches get no php.net release. For 7.4, 8.0 and 8.1, the PHP security team published source code fixes for people who build PHP themselves (php-src branches such as PHP-8.1-CVE-2026-109618-109619).

How PHP runs changes the risk:

  • Apache with mod_php (PHP loaded inside Apache): highest risk. A working exploit (ready-made attack code) needs no login. It works while PHP reads a multipart request (form data with file uploads), before your code runs.
  • PHP-FPM (a separate PHP service): the PHP Group calls it exposed, but says nobody has shown a complete FPM exploit for this CVE.
  • FrankenPHP: likely affected like mod_php.
  • LiteSpeed with LSAPI: the same group expects exploits for specific applications but has confirmed none.

An attack's success depends on the PHP build, extensions, web server and memory layout.

How to check your version

On the server, run:

shell
php -v

Your web server may use a different PHP from the command line. Create a temporary file in your site's public folder with the line below:

php
<?php echo phpversion(), ' ', php_sapi_name();

Open it in a browser, then delete it.

apache2handler means mod_php; fpm-fcgi means PHP-FPM. In WordPress, read Tools > Site Health > Info, Server section.

Ubuntu and some RHEL versions keep the old version number in their patched packages. Debian moved to the new PHP versions (8.2.35-1deb12u1 on bookworm, 8.4.27-1deb13u1 on trixie). If php -v shows an older version, search the package's list of changes for the CVE ID. On Ubuntu (replace 8.3 with your branch):

shell
zgrep CVE-2026-109618 /usr/share/doc/php8.3-common/changelog.Debian.gz

On RHEL, AlmaLinux or Rocky:

shell
rpm -q --changelog php-common | grep CVE-2026-109618

On Docker, check that your official php image tag is at or above your branch's fixed release. Official images for 8.1 and older get no fix.

What to do now

  1. Update PHP to 8.2.35, 8.3.36, 8.4.27, 8.5.12 or later in your branch, or install your OS supplier's patched package. That package may keep the old version number. Only a PHP build with the patch fully fixes the flaw.
  2. On older branches, install your OS supplier's patched package if one exists. If you build PHP yourself on 7.4, 8.0 or 8.1, use the PHP team's source code fixes. On 7.3 or older with no such package, upgrade to a supported branch. On shared hosting, ask your host.
  3. Set session.upload_progress.enabled=0 in php.ini, the FPM pool or the server config (not ini_set() or .user.ini). This blocks the confirmed session upload-progress path of CVE-2026-109619. It does not block that flaw's other variants. It also fully covers the related CVE-2026-115560, announced on 23 October 2026. Keep it until PHP's next regular release.
  4. Restart Apache and every PHP-FPM pool to load the changes.

If you cannot update today, set memory_limit=-1 with php_admin_value to remove the memory cap, then restart PHP. If your app does not use multipart requests, block them at the web server or firewall. Neither step fully closes the flaw. Do not use RLIMIT_AS or RLIMIT_DATA memory caps: they trigger the bug. On PHP 8.5, also set fatal_error_backtraces=0 and restart every worker. This blocks only the confirmed fatal-backtrace attack path of CVE-2026-109619.

Wiz, one of the teams that reported the flaw, lists these signs of an attack:

  • multipart requests, then memory-limit errors or repeated HTTP 500 errors
  • oversized or malformed PHPSESSID session cookies in PHP's responses
  • PHP processes restarting without a clear cause

Is it being exploited?

On 23 October 2026, this CVE was not in the Known Exploited Vulnerabilities catalog of CISA, the US cyber defence agency. That list covers flaws used in real attacks. On 21 October 2026, the release day, the agency's own assessment recorded no known attacks.

The same day, Cloudflare wrote that this CVE and CVE-2026-109619, which researchers call php2shell, leaked before release. It saw attacks on its customers that were changed to try to get around its web application firewall rules. Its post covers both flaws and still says to update PHP.

Sansec says Cloudflare reported early attacks at 07:43 UTC that day, before the 14:00 UTC release. Sansec adds that the public exploits fail against a default PHP install. Most need a local file inclusion bug (a flaw that makes the app load a file the attacker picks) in the target app. None of these reports describes a confirmed break-in through this CVE.

Get help

Updating closes this flaw. Flaws in your own code get no CVE and no update, and a test of your app is how they are found.

Web app and API security test

A penetration test of your web app and its API: who can see whose data, and what an attacker can change.

From AED 20,000, excl. 5% VAT

Ask for a quote Book a call

Sources

  1. RCE via OOM corruption (GHSA-w8hw-w9fx-j79w) PHP Group (php-src)
  2. Security advisory: Critical remote code execution vulnerabilities, update now (21 October 2026) php.net
  3. CVE-2026-109618 detail NIST NVD
  4. PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet Wiz Research
  5. Cloudflare deploys protections against php2shell vulnerability Cloudflare
  6. PHP2Shell: PHP RCE (CVE-2026-109618, CVE-2026-109619) Sansec

The same update also fixes CVE-2026-109619.

More CVE alerts

All CVE alerts