[Security Notice] Node.js runtime vulnerabilities in Function Compute and recommended fixes

Updated at:

Node.js released security versions that fix 10 vulnerabilities. This notice describes the affected scope of the Node.js runtime in Function Compute and the recommended fixes.

Background

On October 21, 2026, Node.js released security versions for 22.x, 24.x, and 26.x to fix 10 security vulnerabilities. The highest severity rating is High. CVE-2026-111497 is an out-of-bounds write in the Brotli decoder and can lead to remote code execution. For details about the vulnerabilities, affected versions, and fixed versions, see Node.js official security advisory.

Node.js also confirms that when a security release occurs, every version that no longer receives official security maintenance (end of life, EOL) is considered affected. The built-in Node.js runtimes of Function Compute (nodejs12, nodejs14, nodejs16, nodejs18, and nodejs20) are all built on Node.js versions that have reached EOL. These runtimes are not covered by this official fix. The following table describes the affected runtime modes and the recommended fixes. Check your workloads against the table and apply the recommended fixes as soon as possible.

Affected scope

Runtime mode

Impact

Recommended action

Built-in Node.js runtimes of Function Compute 2.0 / Function Compute 3.0 (nodejs12, nodejs14, nodejs16, nodejs18, and nodejs20)

These runtimes are built on upstream EOL versions, and no official fixed version is available. The call chain of the platform runtime itself does not constitute a known trigger path. The risk depends on whether the function code and its dependencies use the affected features to process untrusted input. These features include Brotli decompression, Domain Name System (DNS) resolution, Transport Layer Security (TLS) certificate verification, and HTTP keep-alive.

Migrate to a custom runtime (custom.debian10 or later) and use a fixed version of the Node.js public layer. For more information, see Node.js public layer versions and upgrade recommendations below. If you cannot migrate at this time, contact Function Compute technical support.

Custom runtime + Node.js public layer

The impact depends on the Node.js version that the layer provides. The 22.x versions earlier than 22.23.4 and the 24.x versions earlier than 24.22.1 do not contain all the fixes in this release.

Upgrade to Nodejs22 v4 or later, or Nodejs24 v2 or later, as listed in the Node.js public layer versions and upgrade recommendations table below. After the upgrade, complete compatibility verification and replace existing instances.

Custom container, or Node.js bundled in a custom runtime

The impact depends on the Node.js version in the image or runtime.

Upgrade Node.js to 22.23.4, 24.22.1, or a later version, and then rebuild and publish the image.

Node.js 20.x and earlier versions have reached the end of official security support. No official fixed version exists for these versions, and no fixed Node.js public layer is provided. If you use an unofficial Node.js public layer, or bundle Node.js in a custom runtime or a custom container, upgrade Node.js to 22.23.4, 24.22.1, or a later version.

Solution

The interpreter and the call chain of the built-in Node.js runtimes reside in fixed paths of the platform image, so a public layer cannot overwrite them. No official fixed version exists for these Node.js versions. For the built-in runtimes, migrate to a custom runtime and use a fixed version of the Node.js public layer. If you cannot migrate at this time, contact Function Compute technical support.

Node.js public layer versions and upgrade recommendations

Public layer

Compatible runtime / Node.js baseline

Version not recommended

Recommended version

Nodejs22

custom.debian10, custom.debian11, custom.debian12 / Node.js 22.23.4

Earlier than v4

v4 or later

Nodejs24

custom.debian10, custom.debian11, custom.debian12 / Node.js 24.22.1

Earlier than v2

v2 or later

Other Node.js public layers earlier than Node.js 22

None

All existing versions

None. Upgrade to the Nodejs22 or Nodejs24 public layer.

  • The versions in this table are the values of /versions/N at the end of the Alibaba Cloud Resource Name (ARN) of 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, use the Nodejs24 public layer, which is based on Node.js 24 Long Term Support (LTS). Complete 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