Checking AWS's Announcement Regarding the November 2026 PHP Security Release

Checking AWS's Announcement Regarding the November 2026 PHP Security Release

Based on AWS Security Bulletin 2026-190-AWS: how to apply the fixed PHP versions (8.2.36 / 8.3.37 / 8.4.28 / 8.5.13) on Amazon Linux 2023, plus AWS WAF measures and guidance by AWS configuration.
2026.11.20

This page has been translated by machine translation. View original

Introduction

On November 19, 2026, AWS Security Bulletin 2026-190-AWS (hereinafter, the Bulletin) announced a PHP Foundation security release. The fixed versions are 8.2.36 / 8.3.37 / 8.4.28 / 8.5.13.

https://aws.amazon.com/security/security-bulletins/2026-190-aws/

This release fixes 17 issues. These include issues that, under certain conditions, allow an unauthenticated remote third party to make a PHP process unresponsive, access process memory, or execute code. In this article, I verify the steps for applying the fixed packages on new and old Amazon Linux 2023 AMIs. I also summarize the scope of the AWS WAF PHP managed rule group and the response for each AWS configuration.

Test environment

On November 20, 2026, I launched two t3.small (x86_64) instances in ap-northeast-1. I ran commands with root privileges from SSM Run Command. The two AMIs are as follows.

Release timing AMI name
New AMI November (latest) al2023-ami-2023.12.20261119.0-kernel-6.18-x86_64
Old AMI August al2023-ami-2023.12.20260831.0-kernel-6.1-x86_64

Fixed packages for Amazon Linux 2023

PHP versions included in the new and old AMIs

I checked the php8.1–8.5 packages provided by each AMI with dnf list available 'php8.?'.

Package New AMI Old AMI
php8.1 8.1.34-1.amzn2023.0.1 8.1.34-1.amzn2023.0.1
php8.2 8.2.36-1.amzn2023.0.1 8.2.33-1.amzn2023.0.1
php8.3 8.3.37-1.amzn2023.0.1 8.3.33-1.amzn2023.0.1
php8.4 8.4.28-1.amzn2023.0.1 8.4.24-1.amzn2023.0.1
php8.5 8.5.13-1.amzn2023.0.1 8.5.9-1.amzn2023.0.1

php8.1 remains at 8.1.34 in both AMIs. PHP 8.1 and earlier are EOL and no fixes are provided. However, some issues, including CVE-2026-129289, also affect 8.1 and earlier, so the Bulletin recommends migrating to a supported branch.

I installed php8.4 on both the new and old AMIs with the same command and compared the first line of php -v.

dnf install -y php8.4 php8.4-fpm
php -v
# 新 AMI
PHP 8.4.28 (cli) (built: Nov 17 2026 20:29:32) (NTS gcc x86_64)

# 旧 AMI
PHP 8.4.24 (cli) (built: Jul 29 2026 05:29:50) (NTS gcc x86_64)

On the new AMI, the fixed version is installed without any additional work. On the old AMI, a plain install gives you the pre-fix 8.4.24.

Upgrading the old AMI

I updated php8.4 on the old AMI to 8.4.28 using a command in the format described in the Bulletin.

dnf upgrade -y --releasever=latest php8.4-8.4.28-1.amzn2023.0.1

The following 10 packages were updated.

Upgraded:
  php8.4-8.4.28-1.amzn2023.0.1.x86_64                                           
  php8.4-cli-8.4.28-1.amzn2023.0.1.x86_64                                       
  php8.4-common-8.4.28-1.amzn2023.0.1.x86_64                                    
  php8.4-fpm-8.4.28-1.amzn2023.0.1.x86_64                                       
  php8.4-mbstring-8.4.28-1.amzn2023.0.1.x86_64                                  
  php8.4-opcache-8.4.28-1.amzn2023.0.1.x86_64                                   
  php8.4-pdo-8.4.28-1.amzn2023.0.1.x86_64                                       
  php8.4-process-8.4.28-1.amzn2023.0.1.x86_64                                   
  php8.4-sodium-8.4.28-1.amzn2023.0.1.x86_64                                    
  php8.4-xml-8.4.28-1.amzn2023.0.1.x86_64                                       

Complete!

The command specified only php8.4, but related packages including php8.4-fpm were updated at the same time. After the update, php -v showed 8.4.28, the same as the new AMI.

PHP 8.4.28 (cli) (built: Nov 17 2026 20:29:32) (NTS gcc x86_64)

According to the Bulletin, obtaining the fixed versions on AL2023 requires release 2023.12.20261119.0 or later. If you have pinned the release version, move the pin to this release or later.

Restarting php-fpm

The Bulletin advises restarting services that run PHP, such as php-fpm and httpd, after updating the packages. On the old AMI, with httpd not running and only php-fpm started, I looked at the master process PID before and after the upgrade and at the systemd log.

ps -o pid,lstart,cmd -C php-fpm
journalctl -u php-fpm --no-pager -o short-iso

The master process PID was 25729 before the upgrade and 26089 after the upgrade (before a manual restart). The journal recorded php-fpm.service stopping and starting again at 00:19:52, during the upgrade run (00:19:25–00:19:53 UTC). The following is an excerpt of the relevant lines, with the ends of the lines omitted.

2026-11-20T00:19:52+0000 <hostname> systemd[1]: Stopping php-fpm.service - The PHP FastCGI Process Manag
2026-11-20T00:19:52+0000 <hostname> systemd[1]: Started php-fpm.service - The PHP FastCGI Process Manage

In this configuration, the php-fpm master process was replaced during the update even without a manual restart. To check whether it was restarted in your own environment, compare the master process PID before and after the update with ps, or look for the stop and start records with journalctl.

AWS WAF PHP managed rule group

The Bulletin lists 7 critical issues, and 2 of them were added as detection targets in Version 2.6 of the PHP managed rule group.

PHP2Shell_BODY, added in Version 2.3 in October, and PHP2Shell_BODY_Extended, added in 2.4, are introduced in the following article.

https://dev.classmethod.jp/articles/aws-waf-php2shell-body-managed-rule/

New rules in Version 2.6

I retrieved the Version_2.6 rules using the API with REGIONAL scope (ap-northeast-1).

aws wafv2 describe-managed-rule-group --scope REGIONAL --vendor-name AWS --name AWSManagedRulesPHPRuleSet --version-name Version_2.6 --region ap-northeast-1

The rules that are not in Version_2.5 and were added in Version_2.6 are the following two (excerpt). The actions of the other 6 rules are Block in both 2.5 and 2.6.

        {
            "Name": "PHPUploadProgressSerializedObject_BODY",
            "Action": {
                "Count": {}
            }
        },
        {
            "Name": "PHPFPMSmuggling_BODY",
            "Action": {
                "Count": {}
            }
        },

The target CVEs and what each rule detects in the following table are based on the Bulletin.

Rule name Target CVE What it detects
PHPUploadProgressSerializedObject_BODY CVE-2026-115560 Unexpected serialized object syntax contained in PHP upload progress values and multipart file metadata
PHPFPMSmuggling_BODY CVE-2026-129289 Binary-encoded FastCGI parameters embedded in the HTTP request body

The default version at the time of testing is Version_2.5. If you want to use the latest version, change the version of the rule group added to your Web ACL to Version 2.6, and we recommend first evaluating it with the action left as Count.

CVEs without a managed rule

The reasons in the following table are based on the Bulletin.

CVE Why there is no managed rule
CVE-2026-129182 The issue depends on PHP's shutdown settings and worker state, and abnormal requests may be indistinguishable from normal traffic
CVE-2026-129474 The valid JSON and whitespace contained in abnormal requests can also appear in normal requests. The impact depends on application memory usage, magic method execution, and PHP settings
CVE-2026-129481 Memory corruption can occur from the combination of stale PHP worker state left over after a failed session cleanup and subsequent requests to the same worker. It depends on application behavior and worker history
CVE-2026-126714 An abnormal payload looks like ordinary serialized data, and the subsequent session update and read also look like ordinary traffic. Exploitation requires that a session file write be interrupted on the server side, and WAF may not be able to reliably detect it from the request
CVE-2026-129496 Requests exceeding PHP's input limits and some malformed uploads can cause diagnostic log output that triggers the issue. These also appear in normal traffic and are not distinctive enough to be distinguished

Response by AWS configuration

I summarized the required response in AWS environments, centered on the Bulletin's content.

Configuration Response
Amazon Linux 2023 Updated php8.2–8.5 packages are available in all Regions. Run the update command that matches the PHP version you use, and restart the services that run PHP. An OS reboot is not required
Amazon Linux 2, Amazon Linux 2027 Preview Updated packages are being prepared for publication. The Bulletin will be updated when they are published, so wait for their release
AWS Elastic Beanstalk For environments using managed platform updates, the updated platform is applied during the configured maintenance window. For environments that do not use them, update to the latest PHP platform version
Amazon Lightsail PHP on existing instances is the customer's responsibility. Update PHP on the instance
Amazon EC2, Amazon ECS, Amazon EKS, AWS Fargate PHP in your own instances and container images is the customer's responsibility. Update Amazon Linux using the steps above. For other distributions or builds from source, follow the provider's guidance or update to the fixed version of the PHP branch you use. To apply the change, restart the PHP services, or rebuild and redeploy the image
AWS Lambda There is no managed PHP runtime. If you use PHP with a custom runtime or a container image, update PHP and redeploy the function
AWS WAF PHP managed rule group Version 2.6 adds new rules covering 2 of the critical issues. Address the remaining 5 critical issues by updating PHP

Summary

For Amazon Linux 2023, the fixed versions are distributed in release 2023.12.20261119.0 and later. In environments that meet the conditions for being affected by the vulnerabilities, we recommend moving the release version to this release or later and applying the fixed versions.

The AWS WAF PHP managed rule group adds new rules in Version 2.6 covering 2 of the 7 critical issues. Address the remaining 5 by updating PHP. If you use the PHP managed rule group, please try Version 2.6.

Share this article

AWSのお困り事はクラスメソッドへ