BTC$64,746-0.32% LTC$44.82-1.16% XMR$495.04-0.96%
TorPortal TorPortalMarkets, mirrors, dark web news
BleepingComputer · Oct 23, 2026 · 2 min read · Original story

PHP shares mitigation for new RCE vulnerability with no patch

PHP shares mitigation for new RCE vulnerability with no patch

The PHP security team has shared mitigation measures for a new remote code execution vulnerability that affects systems with non-default configurations and has no patch.

PHP is an open-source web development language used by nearly 70% of all websites on the Internet. According to VirusTotal estimates, more than 5.1 million PHP hosts are exposed online, and roughly 3.8 million have at least one port open to attacks.

According to a Friday advisory, this security flaw (tracked as CVE-2026-115560) can only be exploited when targeting systems "with an unusual combination of configuration and application code."

"An application must set session.serialize_handler to php_binary or php_serialize in its configuration and then switch it to php at runtime with ini_set() before calling session_start(). Session upload progress must also still be enabled," the PHP team explained.

"Applications that never change the serialize handler at runtime can keep the feature enabled. Since this setup is unlikely in practice, we are handling it in the regular release cycle and will publish a full advisory for CVE-2026-115560 with the next release."

Until a security patch is available, the PHP devs suggested setting session.upload_progress.enabled=0, adding that "If you applied it then, keep it in place and no further action is needed."

This mitigation should have already been applied on Wednesday, before patching two other critical RCE vulnerabilities (CVE-2026-109618 and CVE-2026-109619) tracked collectively as PHP2Shell.

PHP2Shell flaws now targeted in attacks

The PHP security team patched the PHP2Shell vulnerabilities one day after urging admins to prepare to install the updates as soon as they became available.

While some proof-of-concept (PoC) code was published before the patches went live, the PHP security team said none were functional.

However, multiple cybersecurity companies (including Cloudflare, watchTowr, Previdian, Hadrian, and Patchstack) detected unsuccessful exploitation attempts before public disclosure, after some details on the PHP2Shell security flaws (including the CVE IDs and mitigation advice provided to some critical infrastructure providers) leaked online.

Security researchers at Amazon Threat Intelligence also said that attackers began targeting the PHP2Shell vulnerabilities four days before security patches were released on Wednesday.

"The actual payloads and choices in anonymization infrastructure varied, suggesting these were multiple actors. Technical analysis is ongoing, and it's unclear if any of these attempts would have succeeded in real-world systems," said AWS chief information security officer CJ Moses.

"PHP2Shell is now seeing broad exploitation attempts in the wild," he added, though it's unclear how many attacks (if any) have succeeded.

Dataminr's Threat Research and Cyber Engineering (TRACE) team also said in a Thursday report that "observed activity since vulnerability disclosure remains limited to scanning, fingerprinting, and use of non-working exploits, with no known compromises," but noted that "it remains only a matter of time for working POCs or successful exploitation activity to emerge."

References in this story

  1. Usage Statistics and Market Share of PHP for Websites, October 2026 w3techs.com How many websites are using PHP
  2. Sizing the PHP exposure window for CVE-2026-109618 and CVE-2026-109619 with VirusTotal blog.virustotal.com On October 20, the PHP security team announced an out-of-band security release for Wednesday, October 21, 2026 at 14:00 UTC , fixing two cr...
  3. PHP www.php.net PHP is a popular general-purpose scripting language that powers everything from your blog to the most popular websites in the world.
  4. PHP ships emergency patches for critical PHP2Shell flaws www.bleepingcomputer.com The PHP security team released emergency security patches for two critical remote code execution (RCE) vulnerabilities (CVE-2026-109618 and CVE-2026-109619) tracked collectively as PHP2Shell.
  5. PHP warns admins of two critical flaws, emergency patches coming tomorrow www.bleepingcomputer.com The PHP security team is warning administrators to prepare for emergency security updates tomorrow to address two critical vulnerabilities, as information about the flaws has reportedly leaked ahead of their scheduled…
  6. Cloudflare deploys protections against php2shell vulnerability blog.cloudflare.com Cloudflare has deployed default web application firewall (WAF) protections for newly disclosed PHP vulnerabilities before public disclosure. The rules use request and response signals to stop exploit attempts and…
  7. CVE-2026-109619: PHP Remote Code Execution Exploited watchtowr.com CVE-2026-109619: PHP Remote Code Execution lets attackers run code; update to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35. Exploited in the wild per watchTowr.
  8. Previdian (@PrevidianCyber) on X x.com We're now seeing upload progress probes for PHP’s critical RCE vulnerability, CVE-2026-109618. Our honeypots captured three HTTP requests from two source IPs, including PHP test code embedded in upload filenames…
  9. php2shell: Leaked critical PHP RCEs (CVE-2026-109618, -109619) hadrian.io Two critical PHP core RCEs (CVSS v4.0 9.2) leaked before PHP's 21 October fix. What is confirmed, what is rumor, and how to prepare your PHP estate now.
  10. Oliver Sild (@OliverSild) on X x.com ⚡️Active exploitation attempts of PHP2Shell confirmed by Cloudflare and by multiple web hosting partners of @patchstackapp (has been going on for hours already).
  11. Today thephp.foundation Describing the story behind how critical security vulnerabilities were found and fixed.
  12. Amazon Threat Intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot | Amazon Web Services aws.amazon.com Amazon Threat Intelligence identified a PHP2Shell exploitation attempt dating to Oct. 17, 2026, in MadPot telemetry, four days before public disclosure of CVE-2026-109618 and CVE-2026-109619. The exploit attempt…

Guides related to this story

← Back to all news