"The PHP Foundation has released security patches for a new set of 18 vulnerabilities, seven of which are marked critical."
Scope of the November 19 release and timing
On 19 November 2026 the PHP Foundation published security patches addressing 18 vulnerabilities that affect all supported PHP versions. The release is part of PHP’s regular four-week cycle and accompanied new version builds — 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6 — published alongside the fixes. The foundation warned users about the vulnerabilities on 18 November and urged administrators to prepare to upgrade once patched versions became available.
PHPAfterShell (CVE-2026-126714): session-file handling can lead to RCE
One of the newly disclosed critical flaws, dubbed "PHPAfterShell" and tracked as CVE-2026-126714, was discovered by security firm Depthfirst using AI frontier models tuned for cybersecurity tasks. The issue resides in PHP’s session handling when using the default file-based storage (session.save_handler = files). By manipulating a session while a file is being uploaded, an attacker could trick the server into executing arbitrary code.
Successful exploitation could allow a remote attacker to read sensitive information (including login credentials and customer records), modify session data, spy on visitors or disrupt services. The vulnerability affects PHP 8.5 versions earlier than 8.5.13, PHP 8.4 versions earlier than 8.4.28, PHP 8.3 versions earlier than 8.3.37 and PHP 8.2 versions earlier than 8.2.36. PHP 8.1 and earlier are noted as end-of-life.

Your scanner finds 4,000 vulns. Which 12 matter?
Nubivance is a Rapid7 Registered Partner delivering vulnerability management as a service - scanning, risk-based prioritization, and remediation follow-through across IT and OT.
Fix the backlogOther critical and high-risk flaws in the November release
Alongside PHPAfterShell, the release fixed multiple high-severity memory-corruption and request-handling flaws. Notable entries include:
- CVE-2026-129481 (CVSS 9.2): use-after-free triggered by interrupted session shutdown, potentially allowing memory corruption and remote code execution
- CVE-2026-129474 (CVSS 9.2): use-after-free in magic method backtraces that could allow arbitrary code execution
- CVE-2026-129182 (CVSS 9.2): use-after-free when repopulating the last fatal error backtrace after shutdown, potentially leading to remote code execution
- CVE-2026-129496 (CVSS 9.2): use-after-free in the time zone cache that could lead to remote code execution
- CVE-2026-129289 (CVSS 9.2): request-smuggling caused by unread HTTP request bodies, potentially allowing attackers to manipulate request processing
- CVE-2026-129291 (CVSS 8.8): use-after-free in PHP-FPM's epoll event handling that could enable local privilege escalation
- CVE-2026-128090 (CVSS 7.7): OpenSSL signature verification bypass via algorithm downgrade, potentially letting malicious PHAR archives pass signature checks
- CVE-2026-129538 (CVSS 6.9): out-of-bounds read/write in PHP-CGI when correcting PATH_INFO, potentially causing memory corruption
- CVE-2026-129292 (CVSS 5.3): XSS in the PHP-FPM status endpoint due to insufficient escaping
- CVE-2026-129506 (CVSS 6.3): use-after-free when processing DTD entity references, potentially causing memory corruption
- CVE-2026-128064 (CVSS 8.2): mixed-case HTTPS and FTPS URLs could cause sensitive information to be sent in plaintext
- CVE-2026-127960 (CVSS 8.7): denial-of-service via folded HTTP response headers
- CVE-2026-129438 (CVSS 6.3): incorrect RFC 3986 URI serialization for oversized input
- CVE-2026-15353 (CVSS 6.3): information disclosure with malformed array dimensions during SOAP processing
- CVE-2026-129501 (CVSS 6.3): double-free during DOM XML serialization causing memory corruption and denial of service
- CVE-2026-48841 (CVSS not published): vulnerability in bundled uriparser library mitigated by upgrading that dependency to version 1.0.3
One earlier-disclosed RCE, CVE-2026-115560 in session upload progress, was published by PHP on 23 October; it requires a highly specific and unlikely combination of conditions to exploit.
Real-world exploitation after PHP2Shell: security gateways, ESXi and firewalls
These November fixes arrive a month after disclosure of two critical PHP flaws tracked as CVE-2026-109618 and CVE-2026-109619, collectively known as "PHP2Shell." That earlier disclosure was followed by documented exploitation attempts and compromises against internet-facing systems.
Check Point reported campaigns exploiting PHP2Shell against its own security gateways dating back to 30 October. The attacks involved deployment of backdoors and destructive tools targeting VMware ESXi virtualization servers. Attack activity also extended to Palo Alto Networks firewalls, with attackers targeting devices whose administrative interfaces were exposed to the internet. Those incidents demonstrated the practical consequences of leaving vulnerable PHP installations unpatched.
How FrankenPHP, Docker and Laravel are preparing updates
Open-source maintainers and downstream distributors are already working to incorporate the PHP fixes. Kevin Dunglas, creator of FrankenPHP — a modern PHP application server built around the Caddy web server — said on X that FrankenPHP is working with The PHP Foundation and Docker to provide updated builds as soon as patched PHP versions are available. Planned outputs include static binaries, RPM and DEB packages, Homebrew packages and Docker images based on Debian and Alpine Linux.
Laravel said on X it is working on a remediation plan to protect applications running across its hosting and deployment services. The broader community of maintainers and distributions was described as actively incorporating fixes so patches can reach downstream users quickly.
For organizations running PHP, the immediate task is clear from the record: patches were released on 19 November, PHP warned users on 18 November, and maintainers are already coordinating updates. Whether those patched builds reach every internet-facing appliance and hosted environment before attackers exploit the remaining windows of opportunity will be a measure of how rapidly this patch cycle is applied.




