PHP Foundation releases fixes for critical security flaws


The updates address flaws that could let attackers run code on affected servers, with exposure depending on the application and its configuration.
Situation: PHP2Shell critical vulnerability
The PHP Foundation released security updates on 19 November 2026, for multiple critical flaws, including vulnerabilities that could allow remote code execution: an attacker running instructions on an affected server. Depending on the flaw, that code could run with the privileges of a PHP worker, the process handling an application’s requests.
The release follows emergency fixes for two separate flaws, CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell. The US Cybersecurity and Infrastructure Security Agency added those earlier flaws to its catalog of known exploited vulnerabilities on 26 October.
The Hacker News lists seven flaws with a critical severity score of 9.2. The versions in the table are those listed as fixed; the list alone does not establish that every earlier version was affected.
| Flaw | Fixed releases |
|---|---|
| CVE-2026-115560, CVE-2026-126714, CVE-2026-129289, CVE-2026-129496 | PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0 |
| CVE-2026-129182, CVE-2026-129474 | PHP 8.5.13, 8.6.0 |
| CVE-2026-129481 | PHP 8.3.37, 8.4.28, 8.5.13, 8.6.0 |
The advisory for CVE-2026-115560 says command execution was reproduced on PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Older unsupported releases may also be affected, it says, because the session upload progress feature was introduced in PHP 5.4.0. Separately, CVE-2026-129474 could allow remote code execution on PHP 8.5 and later under particular application conditions.

404 Media reports precautionary shutdowns after researchers found flaws in PHP, a programming language used to run websites, prompting government instructions for immediate fixes.
Another fixed flaw, CVE-2026-129291, has a severity score of 8.8 and could allow local privilege escalation. Unlike the remote-code-execution risks, exploiting it requires code already running in an FPM worker, along with specific worker-pool and event-backend settings.
Two of the critical flaws involve sessions, which store information an application uses across requests. CVE-2026-115560 can arise when session data is written in one format and read in another, including across separate applications sharing storage. Code execution also requires suitable application code that can be misused when the data is read.
CVE-2026-126714 concerns interrupted writes to file-based sessions. Exploitation requires an attacker to influence session data, interrupt a write at a useful point and find suitable application code to misuse.
The PHP advisories recommend upgrading to the fixed release for the relevant branch. As a temporary measure, operators who do not need session upload progress can disable it administratively before request input is processed; calling ini_set() from the application is too late; the advisory for the file-write flaw also recommends limiting untrusted data stored in sessions. Disabling upload progress alone does not fix applications that independently store attacker-controlled session data.
The serializer fix disables session upload progress by default, but an explicit setting can turn it back on. The advisory says configurations that share session data must use matching serializers if the feature remains enabled, even after updating.
PHP published an informational advisory for CVE-2026-115560 on 23 October, after the PHP2Shell emergency releases. PHP Foundation executive director Elizabeth Barron told The Register that the separate flaw did not receive an emergency fix because it required an unlikely combination of configuration and application code and could be mitigated through a setting.
Users of the existing PHP 8.2.x through 8.5.x branches are advised to install the latest release for their branch.
2 min

CISA added the flaws on 26 October 2026, and required federal civilian agencies to address them by 29 October. Palo Alto Networks warned on 28 October 2026, that attackers were exploiting its internet-exposed management interfaces, prompting guidance to restrict access and apply fixes.
3 min

Four fixed PHP releases are available. Operators using PHP 8.1 or older should upgrade or ask their vendor about a fix for their existing version.
9 min