Introduction
nginx2root is a collection of five distinct nginx vulnerabilities and one Linux kernel vulnerability. On November 18, 2026, NGINX released versions 1.30.7 and 1.31.9, which include fixes for several vulnerabilities: CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, and CVE-2026-113425.
This article covers the impact of nginx2root for Mendix apps that run on SAP Business Technology Platform or are deployed using the CloudFoundry or Docker buildpacks.
Environment
Applications hosted in SAP Business Technology Platform
Applications deployed with CloudFoundry buildpack
Applications deployed with Docker buildpack
Details
The NGINX included in the CloudFoundry and Docker buildpacks does not enable the features affected by the most severe of these vulnerabilities (HTTP/2, HTTP/3, resolver and mail proxy) in its default configuration.
As a precaution, a new buildpack release with an upgraded NGINX is being prepared nonetheless. If the NGINX configuration of the buildpack has been customized to enable any of these features, or if an independent NGINX instance runs in front of the applications, upgrading to version 1.30.7, 1.31.9, or later is strongly recommended.
Disable HTTP/2 as a temporary mitigation if an immediate upgrade is not feasible. Note that this workaround addresses only the two specific HTTP/2 vulnerabilities (CVE-2026-123007 and CVE-2026-123633) and does not cover other issues resolved in those releases. Refer to the official NGINX security advisories for further details.
To test whether a deployment uses HTTP/2, execute the following command:
curl -sI --http2 https://example.com
Replace https://example.com with the applicable URL.
Next, examine the first line of the output:
- HTTP/2 200: Indicates that the server successfully communicates via HTTP/2.
- HTTP/1.1 200: Indicates a fallback to HTTP/1.1.
For more detailed diagnostics, run the command in verbose mode to check ALPN (Application-Layer Protocol Negotiation):
curl -sv --http2 -o /dev/null https://example.com 2>&1 | grep -iE 'ALPN|HTTP/2|< HTTP'
Verify that the output confirms the ALPN negotiation:
- ALPN: server accepted h2 (or ALPN protocol: h2): Confirms that HTTP/2 is supported and active.
- Absence of h2: Indicates that HTTP/2 is not negotiated or supported by the target endpoint.
Internal information related
- 292786
- C0CJYEDENSW
0 Comments