Skip to main content

NGINX2Root vulnerabilities in the Embedded Cluster ingress, fixed in the 2026.11.1 release

Issued on November 19, 2026

On Embedded Cluster installations, the bundled ingress controller runs an nginx version affected by CVE-2026-123007 and CVE-2026-123633, known as NGINX2Root. Upgrade to 2026.11.1 as soon as possible: it turns the vulnerable code path off.

What's changing​

Both vulnerabilities sit in the HTTP/2 code of nginx. The Embedded Cluster ingress terminates TLS and HTTP/2 on port 443 of your nodes, with HTTP/2 on by default, so anyone who can reach that port can reach the vulnerable code.

The ingress-nginx project is archived and won't ship a patched controller. In 2026.11.1, we turned HTTP/2 off in the Embedded Cluster ingress. GitGuardian keeps working over HTTP/1.1, and you have nothing to configure.

Who's affected​

  • Affected: Embedded Cluster installations (installed in 2025 or after) running any release from 2025.1.0 to 2026.11.0.
  • Possibly affected, on any installation method: your own nginx or ingress-nginx in front of GitGuardian, if it serves HTTP/2. This includes a reverse proxy built from the example in our network requirements, which enabled HTTP/2 until November 19, 2026. 2026.11.1 doesn't change it.
  • Not affected:
    • The GitGuardian components of Helm and KOTS installations on an existing cluster: they don't use this ingress, and the GitGuardian front pod doesn't serve HTTP/2.
    • Legacy kURL embedded cluster installations.

What you need to do​

Embedded Cluster​

  1. Upgrade to 2026.11.1 from the KOTS Admin Console. Follow Upgrade Embedded cluster, and check the 2026.11 upgrade considerations first.

  2. Until you upgrade, allow port 443 on your nodes only from the networks that use GitGuardian.

  3. Check that HTTP/2 is off. From a machine that can reach a node, run:

    $ openssl s_client -connect <node-address>:443 -alpn h2 </dev/null 2>/dev/null | grep ALPN

    The output reads No ALPN negotiated.

Your own nginx or ingress-nginx​

  • nginx: upgrade to 1.30.7, 1.31.9 or later, or remove http2 from your listen directives.
  • ingress-nginx: the project is archived and has no fixed release. Set use-http2: "false" in the controller ConfigMap.

Harden your nodes (optional)​

Block the SCTP kernel module on every node. It stops a known way to turn code execution in nginx into root on the host:

# echo "install sctp /bin/false" > /etc/modprobe.d/disable-sctp.conf

If lsmod | grep sctp already lists the module, reboot the node.

Timeline​

  • 2025.1.0 to 2026.11.0: the Embedded Cluster ingress serves HTTP/2 with an affected nginx.
  • November 19, 2026: 2026.11.1 turns HTTP/2 off in the Embedded Cluster ingress.

Questions​

Reach out to your Customer Success Manager or email us at support@gitguardian.com.