Skip to content

Vulnerabilities & Patches

PHP patches 18 vulnerabilities in November security updates

The updates cover all supported PHP branches and include seven critical-rated flaws, the PHP Foundation said.

https://breach-signal.com/vulnerabilities/php-patches-18-vulnerabilities-november-updates/

Share

This is a new development in a story we reported earlier: PHP warns of unpatched RCE two days after emergency PHP2Shell patches.

Key facts

  • On November 18, 2026, PHP maintainers warned that forthcoming updates would patch flaws hitting every supported PHP branch, with the top severity listed as critical.
  • CVE-2026-129289 is a critical request smuggling flaw in PHP-FPM with a CVSS score of 9.2.
  • CVE-2026-115560 is a session serializer mismatch defect tied to session upload progress that may enable remote code execution.
  • PHP disclosed CVE-2026-115560 in an October 23, 2026 informational advisory concerning session data handling under certain configurations.

PHP maintainers released security patches on November 19, 2026, that fix 18 vulnerabilities across every supported branch, the project said.

The patches ship as PHP 8.5.13, PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. PHP 8.6 also shipped as part of the November 19, 2026, security release. The updates follow PHP’s normal four-week release schedule, and maintainers warned on November 18, 2026, that the forthcoming patches would hit every supported branch with critical-rated flaws at the top severity.

The PHP Foundation says seven of the 18 newly patched vulnerabilities carry critical ratings and affect all supported versions. Exploiting them calls for non-default configuration or uncommon setups, the PHP security team said, and the same condition applies to the critical-rated issues.

CVE-2026-129289 is a critical request smuggling defect in the PHP FastCGI Process Manager (PHP-FPM) with a CVSS score of 9.2. Aikido says attackers without authentication can execute PHP code remotely on vulnerable servers that reuse PHP-FPM backend connections when specific conditions apply. It applies to certain nginx, Apache, HAProxy, and LSAPI configurations that keep backend links open to PHP-FPM, while ordinary nginx and Apache setups without reused backend connections are not exposed.

The issue comes from unread HTTP request bodies and may let attackers manipulate request processing. Teams that cannot patch right away can disable persistent backend connections between web servers and PHP-FPM so that connections close after each request. Aikido warns that the mitigations do not cover every November vulnerability and urges teams to keep PHP-FPM and LSAPI listeners away from direct exposure to untrusted networks.

Security firm Depthfirst identified PHPAfterShell, tracked as CVE-2026-126714, using AI frontier models built for cybersecurity tasks. The flaw lives in PHP session handling that uses file-based storage, the default session.save_handler = files setting. Vulnerable releases include PHP 8.5 before 8.5.13, PHP 8.4 before 8.4.28, PHP 8.3 before 8.3.37, and PHP 8.2 before 8.2.36, while PHP 8.1 and earlier are end-of-life.

A successful PHPAfterShell attack could let a remote attacker read sensitive information such as login credentials, change session data, spy on visitors, or disrupt the service. Vendor patches reach only supported PHP branches, leaving unsupported releases without fixes.

Third-party maintainer Ondrej Surý has issued patched packages for unsupported PHP versions going back to PHP 5.6. Aikido also published hardened PHP container images carrying backported security fixes for unsupported versions including PHP 5.6, 7.0, 7.1, 7.2, 7.4, and 8.1.

CVE-2026-115560 is a session serializer mismatch flaw tied to session upload progress that may permit remote code execution. PHP disclosed the flaw in an October 23, 2026, informational advisory about session data handling under certain configurations. Exploitation requires a program to set session.serialize_handler to php_serialize or php_binary, switch it to php during execution, then invoke session_start, while session upload progress must stay enabled for the flaw to be exploitable.

Exploiting it calls for a highly specific and unlikely combination of conditions, Infosecurity Magazine reports. PHP advised administrators to turn off session upload progress with session.upload_progress.enabled=0 and restart PHP workers as a temporary fix. PHP said the same step helps mitigate CVE-2026-109619, one of the two PHP2Shell flaws.

Other critical-rated issues include CVE-2026-129474, a magic method backtrace use-after-free flaw carrying CVSS 9.2 and allowing arbitrary code execution, and CVE-2026-129496, a timezone cache use-after-free flaw rated CVSS 9.2 that may lead to remote code execution. The CVE-2026-129291 flaw is a PHP-FPM epoll use-after-free issue that could lead to local privilege escalation and carries CVSS 8.8.

The updates also address CVE-2026-129481, a use-after-free flaw triggered by an interrupted session shutdown and rated at CVSS 9.2, and CVE-2026-129182, a use-after-free linked to the last fatal error backtrace after shutdown, rated at CVSS 9.2. CVE-2026-129501 is a double-free in DOM XML serialization carrying CVSS 6.3 and causing memory corruption and denial of service.

CVE-2026-129538 is an out-of-bounds read and write flaw in PHP-CGI that occurs during PATH_INFO environment variable correction and carries CVSS 6.9. CVE-2026-129292 is a cross-site scripting flaw in the PHP-FPM status endpoint carrying CVSS 5.3. CVE-2026-15353 is an information disclosure flaw tied to malformed array dimensions during SOAP processing with CVSS 6.3.

CVE-2026-129506 is a use-after-free during DTD entity reference processing with CVSS 6.3. CVE-2026-128064 is a mixed-case HTTPS and FTPS URLs flaw rated CVSS 8.2 that could leak sensitive data in plaintext. CVE-2026-127960 is a denial-of-service flaw tied to folded HTTP response headers carrying CVSS 8.7, while CVE-2026-129438 is an incorrect RFC 3986 URI serialization flaw affecting oversized input and carrying CVSS 6.3.

The last item is CVE-2026-48841, a bundled uriparser library flaw with CVSS not published, fixed by upgrading the dependency to version 1.0.3.

The November updates arrive after the October 21, 2026 disclosure of two critical PHP2Shell flaws, CVE-2026-109618 and CVE-2026-109619. That day, the PHP project released PHP 8.5.12, PHP 8.4.27, PHP 8.3.36, and PHP 8.2.35 for those flaws. The PHP2Shell flaws allow unauthenticated remote code execution and were found using frontier AI models.

Researchers have documented real exploitation attempts and system compromises on internet-facing hosts in the weeks after the PHP2Shell disclosure. Check Point said PHP2Shell exploitation campaigns hit security gateways as far back as October 30, 2026, with attackers deploying backdoors and destructive tools on VMware ESXi servers. Attackers also targeted Palo Alto Networks firewalls with internet-exposed administrative interfaces.

OpenAI says frontier AI discovered the PHP2Shell vulnerabilities ahead of attackers, opening what it calls a Defender’s Window. The PHP Foundation said, “We won’t pretend otherwise: the delay was a structural failure.”

Support for PHP 8.2 ends on December 31, 2026. Kevin Dunglas, the creator of FrankenPHP, said on X that his project is working with The PHP Foundation and Docker to ship new builds. The FrankenPHP builds will cover Docker images based on Debian and Alpine Linux, Homebrew packages, RPM and DEB packages, and static binaries.

Laravel said on X that it is building a remediation plan to protect applications across its hosting and deployment services. Open-source maintainers who rely on PHP have begun adding the security fixes to their software and distributions.

Server administrators should update to PHP 8.5.13, PHP 8.4.28, PHP 8.3.37, or PHP 8.2.36 based on the supported branch they run. For CVE-2026-129289, teams unable to install updates can disable persistent backend connections so that connections close after each request. PHP also advised turning off session.upload_progress.enabled=0 and restarting PHP workers as a temporary fix.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *