[Security Notice] PHP runtime vulnerabilities in Function Compute and recommended fixes

Updated at:

The PHP development team disclosed two remote code execution vulnerabilities. Review the affected scope of the PHP runtime in Function Compute and apply the recommended fixes.

Background

The PHP development team disclosed two remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619, on October 21, 2026. Both vulnerabilities are rated Critical, with a Common Vulnerability Scoring System (CVSS) score of 9.2. An attacker can exploit them without authentication, and the vulnerability details and exploit tools are already public in the community.

Check your PHP workloads in Function Compute against the following table and apply the recommended actions at the earliest opportunity. For details about the impacts, risk levels, and fixed versions, see Alibaba Cloud security notice.

Affected scope

Runtime mode

Impact

Recommended action

Built-in PHP 7.2 runtime of Function Compute 2.0 (HTTP handler)

The HTTP handler provided by the platform does not involve any known trigger path. A risk exists only if the function code calls requestPhpCgi() to forward requests to PHP CGI. Check the entire code package, including template and framework adapter code.

Functions whose code does not call requestPhpCgi() to forward requests to PHP CGI require no change. For functions that do call it, migrate to a custom runtime and use a fixed version of the PHP public layer. For more information, see PHP public layer versions and upgrade recommendations in this topic. If you cannot migrate at this time, contact Function Compute technical support.

Built-in PHP 7.2 runtime of Function Compute 2.0 (event handler)

By default, no known trigger path is involved, except for functions whose code adapts web requests on its own, calls a CGI proxy, or starts a PHP web service.

Functions that do not involve trigger paths such as adapting web requests, calling a CGI proxy, or starting a PHP web service require no change. For affected functions, migrate to a custom runtime and use a fixed version of the PHP public layer. For more information, see PHP public layer versions and upgrade recommendations in this topic. If you cannot migrate at this time, contact Function Compute technical support.

Built-in PHP 7.2 runtime of Function Compute 3.0 (event handler)

The platform converts HTTP requests into events before invoking the function. The affected scope is the same as for the built-in PHP 7.2 runtime of Function Compute 2.0 (event handler). By default, no known trigger path is involved, except for functions whose code adapts web requests on its own, calls a CGI proxy, or starts a PHP web service.

Functions that do not involve trigger paths such as adapting web requests, calling a CGI proxy, or starting a PHP web service require no change. For affected functions, migrate to a custom runtime and use a fixed version of the PHP public layer. For more information, see PHP public layer versions and upgrade recommendations in this topic. If you cannot migrate at this time, contact Function Compute technical support.

Custom runtime + PHP public layer

The impact depends on the PHP version in use and its patch status. Prioritize checking workloads that run in web service modes such as PHP-FPM and CGI.

Upgrade to a fixed version of the PHP public layer available in your region. The available versions are listed in the PHP public layer versions and upgrade recommendations table in this topic. After the upgrade, complete compatibility verification and replace existing instances.

PHP 7.2 has reached the end of official security support. No official fixed version exists for PHP 7.2, and no fixed PHP 7.2 public layer is provided. The fixed PHP 8.0 and PHP 8.1 public layers are transitional options for existing workloads. If you use an unofficial PHP public layer, or bundle PHP in a custom runtime, upgrade PHP to 8.2.35, 8.3.36, 8.4.27, 8.5.12, or a later version.

Solution

The interpreter and the call chain of the built-in PHP 7.2 runtime reside in fixed paths of the platform image, so a public layer cannot overwrite them. For built-in runtimes, migrate to a custom runtime and use a fixed version of the PHP public layer. Alternatively, confirm that your function code does not involve any known trigger path listed in the affected scope table. If you cannot migrate at this time, contact Function Compute technical support.

PHP public layer versions and upgrade recommendations

Public layer

Compatible runtime / PHP baseline

Version not recommended

Recommended version

PHP72

custom / PHP 7.2.8

All existing versions

None. Upgrade to a later PHP public layer.

PHP80

custom / PHP 8.0.22

v7 and earlier

v8 or later

PHP81

custom / PHP 8.1.9

v6 and earlier

v7 or later

PHP80-Debian10

custom.debian10 / PHP 8.0.29

v2 and earlier

v3 or later

PHP81-Debian10

custom.debian10 / PHP 8.1.28

v1 and earlier

v2 or later

PHP85-Debian12

custom.debian12 / PHP 8.5.12

None

v1 or later

  • The versions in this table are the values of /versions/N at the end of an Alibaba Cloud Resource Name (ARN) for a layer. A new layer version does not take effect automatically for functions that still reference an earlier version. After you upgrade, make sure that all existing instances are replaced and that regression testing on your workloads is complete.

  • As a long-term recommendation, migrate to a supported PHP version such as PHP85-Debian12. This requires the custom.debian12 runtime and compatibility verification on your workloads.

  • For more information about how to configure a public layer, see Configure official public layers.

If you need assistance, contact Function Compute technical support by submitting an Alibaba Cloud ticket.

References