Published November 20, 2026. We will update this post as new information becomes available.
On November 19, 2026, the PHP development team published security fixes for 17 vulnerabilities affecting supported PHP 8.2, 8.3, 8.4, and 8.5 releases. Seven carry a critical CVSS v4.0 score of 9.2. The issues span several parts of the language and its runtime: PHP-FPM, session handling, SOAP, PHAR archives, HTTP and FTP streams, and newer URI and DOM APIs.
The most severe issues include flaws that can allow remote code execution, but exposure depends on how an application uses PHP and, in some cases, on particular PHP-FPM or php.ini settings. Other fixes address information disclosure, cross-site scripting (XSS), denial of service (DoS), memory corruption, and a local privilege escalation path. The advisories do not describe one shared attack campaign; they document separate vulnerabilities with distinct prerequisites.
Read on to learn about the vulnerabilities, and steps you need to take to protect yourself.
Seven critical vulnerabilities
The critical advisories include several routes to code execution, along with a PHP-FPM request-smuggling issue:
- CVE-2026-129289 (CVSS 9.2): PHP-FPM request smuggling. PHP may fail to discard unread request-body bytes before reusing a persistent FastCGI or LSAPI connection. In the PHP-FPM scenario described by the advisory, an unauthenticated attacker can arrange for leftover bytes to be interpreted as another FastCGI request, potentially bypassing front-end routing and executing PHP code with the worker’s privileges.
- CVE-2026-129496 (CVSS 9.2): timezone-cache use-after-free. Under affected startup and logging conditions, PHP can retain a reference to freed timezone-cache memory. A later diagnostic during early request initialization can trigger memory corruption, a worker crash, and potentially code execution with the PHP worker’s privileges.
- CVE-2026-126714 (CVSS 9.2): partially overwritten session files. If a write to PHP’s default file-based session store is interrupted, the file can contain pieces of both old and new serialized session data. If an attacker can influence session contents and interrupt the write, a later read may deserialize attacker-controlled objects; remote code execution then depends on a suitable object gadget chain in the application.
- CVE-2026-115560 (CVSS 9.2): session serializer mismatch. PHP’s session upload-progress feature can write attacker-controlled data in one serialization format and later parse it using another. A suitable application object gadget chain may turn the resulting interpretation into code execution with the worker’s privileges.
- CVE-2026-129481 (CVSS 9.2): Use-after-free after interrupted session shutdown. This vulnerability affects PHP 8.3 and later and requires specific application behavior, including a fatal error during session cleanup. Exploitation also depends on subsequent requests reaching the same PHP worker, where a stale memory pointer may trigger a use-after-free.
- CVE-2026-129474 (CVSS 9.2): Use-after-free in magic-method backtraces. This vulnerability affects PHP 8.5 and may lead to remote code execution. However, the demonstrated exploitation path requires specific application behavior and non-default PHP configuration settings, including fatal_error_backtraces=1 and zend.exception_ignore_args=0. Notably, PHP’s production configuration sets the latter to 1, preventing the demonstrated exploitation path.
- CVE-2026-129182 (CVSS 9.2): Use-after-free in fatal-error backtraces. This vulnerability affects PHP 8.5 and requires a specific combination of configuration mismatches, shutdown-time errors, and subsequent requests reaching the same PHP worker. These conditions make exploitation dependent on particular server configurations and runtime behavior rather than a straightforward malicious HTTP request.
Other high-severity issues
Four additional vulnerabilities received high-severity ratings, including issues affecting PHAR signature verification, PHP-FPM privilege escalation, and PHP’s network stream wrappers. These vulnerabilities involve server-side operations, local privilege escalation, or outbound network communication rather than attack patterns that can be reliably mitigated through inbound WAF inspection. As such, they fall outside the scope of Imperva Cloud WAF protection. Customers are advised to apply the relevant PHP security updates to address these issues.
Fixed versions
The PHP project released security updates for the 8.2 through 8.5 branches on November 19: PHP 8.2.36, 8.3.37, 8.4.28, and 8.5.13. Administrators should identify the PHP runtime and deployment mode in use, then apply the appropriate vendor-supported update. PHP distributions and managed hosting providers may package the fixes on their own schedules, so teams should verify their actual runtime build rather than relying only on an application dependency manifest.
PHP 8.6.0 was also announced on November 19. The advisories listed above specify affected version ranges in PHP 8.2 through 8.5; consult the individual advisory and the PHP changelog when assessing a particular build or downstream package.
What you should do now
Updating PHP is the primary way to address these runtime flaws. A web application firewall can provide an additional layer of protection by inspecting and filtering malicious HTTP requests before they reach exposed application endpoints, including PHP-FPM-backed services. That layer does not replace updating the PHP runtime, and it cannot address every condition described in these advisories, including vulnerable outbound stream handling, local PHP-FPM master-process paths, or flaws that depend on application behavior and server configuration.
How Imperva Protects You
Imperva provides a set of protections against several of the recently disclosed PHP vulnerabilities.
Cloud WAF, Imperva for Google Cloud, Imperva for AWS and Elastic WAF, provide mitigation for these vulnerabilities, as detailed in the protection status below.
For WAF-GW, manual mitigation steps will be provided as soon as possible and
ADC content, will be released early next week. Protection is not enabled by default. Please contact the support team to enable it in your account.
Protection Status
| CVE | Protection Status | Details |
| CVE-2026-129289 | Protected out of the box | Existing protections mitigate the identified attack vector. We continue strengthening detection across additional variants. |
| CVE-2026-129496 | Opt-in protection available | A dedicated security rule is available for customers to enable. Protection is not enabled by default. |
| CVE-2026-126714 | Protected out of the box | Existing security protections mitigate the identified attack vector. |
| CVE-2026-115560 | Protected out of the box | Existing security protections mitigate the identified attack vector. |
| CVE-2026-129481 | Limited exploitability | Exploitation requires complex, application-specific conditions and particular PHP runtime behavior. |
| CVE-2026-129182 | Limited exploitability
| Exploitation requires specific PHP configuration mismatches and runtime conditions. |
| CVE-2026-129474 | Limited exploitability
| Imperva is evaluating exploitability and potential WAF mitigation opportunities. |
Imperva WAF solutions help protect web applications from malicious HTTP traffic and can reduce exposure to request-based exploit attempts. Organizations should continue to patch PHP and review configuration-dependent exposure as fixes become available from their PHP distribution or hosting provider.
The post PHP Runtime Vulnerabilities: What You Need To Know appeared first on Blog.
