Skip to main content

Kaer NewsSoftware

PHP warns of unpatched remote code execution risk CVE-2026-115560

The PHP security team shared mitigation for a new remote code execution vulnerability affecting systems with non default configurations on 23 October.

3 min read
PHP warns of unpatched remote code execution risk CVE-2026-115560Photo: The Hacker News

Key points

The PHP team issued mitigation advice for an unpatched remote code execution flaw on 23 October.

The PHP security team shared mitigation measures for a new remote code execution vulnerability that affects systems with non default configurations and has no patch available. This advisory arrived on 23 October just two days after emergency patches addressed two critical flaws known collectively as PHP2Shell affecting millions of web hosts online.

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. The PHP team explained that 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.

Conditions for exploitation

Session upload progress must also still be enabled for the vulnerability to be exploitable according to the technical details provided in the advisory. Applications that never change the serialize handler at runtime can keep the feature enabled without immediate risk since this setup is unlikely in practice for most deployed systems.

Until a security patch is available the PHP developers suggested setting session upload progress enabled to zero to mitigate the risk effectively. They added that if you applied it then keep it in place and no further action is needed while the issue awaits resolution in the regular release cycle.

This mitigation should have already been applied on 21 October before patching two other critical remote code execution vulnerabilities tracked collectively as PHP2Shell. The PHP security team patched those vulnerabilities one day after urging administrators to prepare to install the updates as soon as they became available to affected infrastructure.

Previous PHP2Shell attacks

While some proof of concept code was published before the patches went live the PHP security team said none were functional at the time of release. However multiple cybersecurity companies including Cloudflare and Patchstack detected unsuccessful exploitation attempts before public disclosure after some details on the PHP2Shell security flaws leaked online ahead of the embargo.

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 with technical analysis ongoing to determine if any attempts would have succeeded in real world systems.

PHP is an open source web development language used by nearly seventy percent of all websites on the Internet according to estimates provided by VirusTotal. More than 5.1 million PHP hosts are exposed online and roughly 3.8 million have at least one port open to attacks making mitigation critical for organizations.

Patch availability guidance

PHP Project is urging users to act immediately by updating to PHP 8.5.12 8.4.27 8.3.36 or 8.2.35 to address the patched vulnerabilities. Matthew Weier O Phinney principal product manager of Perforce Zend and OpenLogic said that most open source software and commercial LTS software distributions had patches available either at the time of the coordinated release or within a few hours.

The National Security Agency advised heightened awareness of PHP2Shell over the coming weeks saying that any and all vendor issued patches tied to PHP2Shell should be prioritized. Companies should also consider applying mitigative steps such as enhanced logging and replacing end of life PHP packages when appropriate while waiting for further updates.

Frequently asked questions

What is CVE-2026-115560?

CVE-2026-115560 is a new remote code execution vulnerability affecting systems with non default configurations that the PHP team shared mitigation for on 23 October.

How can users mitigate CVE-2026-115560?

Users should set session upload progress enabled to zero until a security patch is available in the regular release cycle to mitigate this specific risk.

When were the PHP2Shell vulnerabilities patched?

The PHP security team patched the PHP2Shell vulnerabilities on 21 October after detecting exploitation attempts and urging administrators to prepare to install the updates.

More from this edition