Skip to main content

PHP Foundation Security Releases – November 19, 2026

Bulletin ID: 2026-190-AWS
Scope: AWS
Content Type: Important (requires attention)
Publication Date: 11/19/2026 10:00 AM PST

Summary:

AWS is aware of security releases that the PHP Foundation published on November 19, 2026. PHP versions 8.2.36, 8.3.37, 8.4.28, and 8.5.13 address 17 issues across the PHP 8.2, 8.3, 8.4, and 8.5 branches. The issues are in the following components:

  • The PHP engine
  • PHP-FPM and the PHP CGI binary
  • The SOAP, Phar, session, DOM, and date extensions
  • The HTTP and FTP stream wrappers
  • The PHP 8.5 RFC 3986 URI implementation

Under specific conditions, some of these issues could allow a remote, unauthenticated third party to cause a PHP process to stop responding, access process memory, or run code in the context of the affected PHP process.

PHP 8.1 and earlier have reached end of life and won't receive these fixes. Some of these issues affect those releases, including CVE-2026-129289. If you run PHP 8.1 or earlier, we recommend that you move to a supported PHP branch.

Patching the affected software remains the only complete fix and should be the first priority. We will update this bulletin as more information becomes available.

Current Mitigation Status:

Amazon Linux: Updated PHP packages that address the CVEs in this bulletin are available for Amazon Linux 2023 in all AWS Regions. Updated packages for Amazon Linux 2 and the Amazon Linux 2027 Preview are being released, and we will update this bulletin when they are available. Amazon Linux 2023: php8.2-8.2.36-1.amzn2023.0.1 (ALAS2023-2026-3504), php8.3-8.3.37-1.amzn2023.0.1 (ALAS2023-2026-3505), php8.4-8.4.28-1.amzn2023.0.1 (ALAS2023-2026-3507), php8.5-8.5.13-1.amzn2023.0.1 (ALAS2023-2026-3506) To update Amazon Linux 2023, run the command for the PHP version you have installed: sudo dnf upgrade --releasever=latest php8.2-8.2.36-1.amzn2023.0.1 sudo dnf upgrade --releasever=latest php8.3-8.3.37-1.amzn2023.0.1 sudo dnf upgrade --releasever=latest php8.4-8.4.28-1.amzn2023.0.1 sudo dnf upgrade --releasever=latest php8.5-8.5.13-1.amzn2023.0.1 If you lock Amazon Linux 2023 to a release version, use release 2023.12.20261119.0 or later. After updating, restart the services that run PHP, such as php-fpm or httpd (for example, sudo systemctl restart php-fpm). A reboot is not required. The advisories are in the repository metadata, so dnf upgrade --security and --advisory find these updates. The metadata does not yet list these CVE IDs; until a later update adds them, CVE-based filters such as --cve and scanners that map fixes by CVE may report these CVEs as unfixed. Amazon Linux Explore shows the current fix status for each CVE, including the Critical CVE-2026-129289, CVE-2026-115560 and CVE-2026-129474.

AWS Elastic Beanstalk: Customers using managed platform updates will receive the updated platform during their configured maintenance window. Other customers should update their environments to the latest PHP platform version.

Amazon Lightsail: Customers running PHP on existing Lightsail instances are responsible for updating PHP on those instances.

Amazon EC2, Amazon ECS, Amazon EKS, and AWS Fargate: Customers who run PHP on their own instances or in container images are responsible for updating PHP. If you use Amazon Linux, update as described above. If you use another distribution or build PHP from source, follow your provider's guidance or upgrade to the fixed release for your PHP branch. Restart PHP services, or rebuild and redeploy container images, for the update to take effect.

AWS Lambda: Lambda doesn't provide a managed PHP runtime. Customers using PHP in a custom runtime or container image are responsible for updating PHP and redeploying their functions.

Additional configuration steps after upgrading:

If you use session upload progress, confirm that all applications and pools that share a session store use the same session.serialize_handler setting. The fixed releases disable session upload progress by default and reject runtime changes to session serialization settings while upload progress is active. They do not enforce matching serializers across separate configurations. If you re-enable session upload progress, review your php.ini files, PHP-FPM pool configurations, virtual host overrides, and command-line jobs to confirm that the serializer settings match.

If you run PHP 8.5, confirm that your production php.ini sets zend.exception_ignore_args=1. This is the value recommended in php.ini-production, and it prevents one of the addressed issues from being reached.

If you maintain forked or derivative PHP code, confirm that it includes these fixes.

Interim step for customers who cannot update immediately:

If you use AWS WAF, we have released version 2.6 of the PHP Managed Rule Group with rules that help protect against attempts to leverage two of these issues. We also provide additional guidance on the five issues for which we are not providing managed rule group. Patching the affected software remains the only complete fix and should be the first priority.

These rules provide protection based on leveraging techniques either observed by our world-wide threat monitoring systems, or reproduced in a test environment by our threat research team. They detect the request patterns we reproduced, but may not detect every issue path or payload variation.

  • PHPUploadProgressSerializedObject_BODY provides coverage for CVE-2026-115560 by detecting unexpected serialized-object syntax in PHP upload-progress values and multipart file metadata.
  • PHPFPMSmuggling_BODY provides coverage for CVE-2026-129289 by detecting binary-encoded FastCGI parameters embedded in HTTP request bodies.

The new rules are initially available in Count mode because they can also block intended traffic. The risk of intended traffic blockage depends on characteristic of your application. We recommend that before switching to Block, leave the rules in Count mode and review their matches using CloudWatch metrics, sampled requests, or AWS WAF logs. This helps confirm that the rules will not block intended requests for your application. To block traffic pin your web ACL to version 2.6 and change the action of the new rules from Count to Block.

Below is a summary of each critical issue:

CVE-2026-115560 - CVSS 9.2 [Use PHPUploadProgressSerializedObject_BODY]

AWS WAF can help mitigate CVE-2026-115560 by detecting unexpected serialized-object syntax in PHP upload-progress values and multipart file metadata. Although patterns are unusual in conventional upload identifiers and filenames, custom applications may still accept such patterns. For this reason we deployed this rule in count mode. Coverage depends on request parsing, field configuration and body inspection limits. Apply PHP security updates, disable unused session upload progress, and ensure all applications sharing session data use the same session serialization format.

CVE-2026-129289 - CVSS 9.2 [Use PHPFPMSmuggling_BODY]

AWS WAF can help mitigate CVE-2026-129289 by detecting length-encoded FastCGI parameter names embedded in HTTP request bodies, which may indicate attempts to leverage requests into PHP-FPM (FastCGI Process Manager). Although these byte sequences are unusual in ordinary application traffic, they may match some intended uploads containing FastCGI captures. For this reason we deployed this rule in count mode. Use this defense-in-depth control alongside PHP security updates or disabling FastCGI connection reuse.

CVE-2026-129182 - CVSS 9.2 [No managed rule available]

For CVE-2026-129182, the anomalous attempts may be indistinguishable from intended traffic because the issue depends on PHP shutdown settings and worker state. The available data does not support a high confidence WAF rule. Apply PHP security updates and restart affected workers. Until patched, review the relevant server settings and set fatal_error_backtraces=0 through effective administrative configuration.

CVE-2026-129474 - CVSS 9.2 [No managed rule available]

For CVE-2026-129474, the anomalous attempts may include valid JSON and whitespace that may appear in intended requests. Its effect depends on application memory usage, magic-method execution and PHP configuration, therefore the available data does not support a high confidence WAF rule. Upgrade to PHP 8.5.13 or later. Until patched, set zend.exception_ignore_args=1 or fatal_error_backtraces=0 in the affected PHP workers and restart them.

CVE-2026-129481 - CVSS 9.2 [No managed rule available]

For CVE-2026-129481, the combination of a stale PHP worker state caused by a failed session clean up and subsequent requests to the same PHP worker, may result in memory corruption. The condition depends on application behavior and worker history, so the available data does not support a high confidence WAF rule. Upgrade to PHP 8.3.37, 8.4.28, 8.5.13 or a later release for your branch, and restart affected workers. Until patched, setting pm.max_requests=1 and restarting PHP-FPM workers prevents the demonstrated cross-request sequence at a performance cost.

CVE-2026-126714 - CVSS 9.2 [No managed rule available]

For CVE-2026-126714, the anomalous payload can look like ordinary serialized data, and the session updates and reads that follow look like normal traffic. Leveraging this issue also depends on a session-file write being interrupted on the server, which a WAF may not reliably detect from the request. For these reasons, a high-confidence WAF rule is not viable, and the fix is to upgrade to PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 or a later release for your branch. For extra hardening, turn off session upload-progress tracking if you don't use it (normal file uploads keep working).

CVE-2026-129496 - CVSS 9.2 [No managed rule available]

For CVE-2026-129496, requests that exceed PHP input limits and some malformed uploads can produce the diagnostics logs that trigger the issue. These request patterns also occur in intended traffic and are not distinctive enough for a high-confidence WAF rule. Upgrade to PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, or later. Until patched, correct the startup diagnostics and restart the PHP master and all workers, or use a logging destination such as syslog that avoids the affected timestamp-formatting path.

References:


Please email aws-security@amazon.com with any s ecurity questions or concerns.