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. For private Mendix deployments, NGINX is part of the infrastructure when it is deployed as an ingress controller or reverse proxy.
This article covers how to identify if the host is affected by nginx2root and how to mitigate the vulnerability for Mendix apps that run on Mendix on Kubernetes, Private Mendix Platform, Windows Service Console and Mendix Portable Runtime.
Environment
Applications hosted in Mendix on Kubernetes
Applications hosted in Private Mendix Platform
Applications hosted in Windows Service Console
Applications hosted in Mendix Portable Runtime
Instructions/Procedure
Mendix on Kubernetes, Private Mendix Platform, Windows Service Console, and Mendix Portable Runtime do not include NGINX by default. When NGINX is deployed in front of these products, such as an ingress controller or reverse proxy, 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.
Outcome
After the mitigation, the app no longer runs the vulnerable nginx on the mitigated host.
Internal information related
- 292786
- C0CJYEDENSW
0 Comments