Security
Nov 19, 2026

NES for Ingress NGINX Patches nginx2root

nginx2root is five NGINX RCE flaws, two of them in HTTP/2, which Ingress NGINX turns on by default. See what NES fixes, how to upgrade, and what to check.

Give me the TL;DR
NES for Ingress NGINX Patches nginx2root

NES (Never-Ending Support) for Ingress NGINX v1.15.1-nes-1.15.12, released November 19, 2026, fixes four of the five remote code execution vulnerabilities in nginx2root: CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, and CVE-2026-121810. The fifth, CVE-2026-113425, is in the mail proxy module, which is not in our build.

The two that matter most, CVE-2026-123007 and CVE-2026-123633, are in NGINX's HTTP/2 code. Neither needs authentication. And Ingress NGINX turns HTTP/2 on by default.

CVE-2026-123634 is narrower. It is reachable on any Ingress that uses external authentication through the auth-url annotation, because the controller resolves the auth service's hostname at request time, in a subrequest. CVE-2026-121810 needs HTTP/3, which the controller only gets through a snippet. We fixed it anyway.

The release also fixes CVE-2026-118899. It is not part of nginx2root, but it is a denial of service that any client can trigger on every TLS server in the default configuration.

The community ingress-nginx project was retired in March 2026, so it will not get a fix.

TL;DR

  • nginx2root is five remote code execution vulnerabilities in NGINX, disclosed November 18, 2026. Two of them, CVE-2026-123007 and CVE-2026-123633, are in HTTP/2 and need no authentication.
  • Ingress NGINX is exposed in its default configuration, because the controller turns HTTP/2 on and proxies every request to a backend.
  • The community ingress-nginx project was retired in March 2026 and will not ship a fix.
  • NES for Ingress NGINX v1.15.1-nes-1.15.12 fixes the four nginx2root CVEs that affect the controller, plus CVE-2026-118899, a denial of service reachable on every TLS server. The fifth nginx2root CVE, in the mail proxy module, is not in our build.
  • If you cannot upgrade today, set use-http2: "false" in the controller ConfigMap. That only blocks the two HTTP/2 CVEs, so treat it as a stopgap.
  • Upgrading does not tell you whether someone already got in. Check for worker crashes and for processes started by NGINX workers.

What is nginx2root?

nginx2root is the name Xint gave to five remote code execution vulnerabilities in NGINX, disclosed on November 18, 2026. Each one is a separate attack path, and each one needs a different configuration:

F5 fixed all five upstream in NGINX 1.30.7 (stable) and 1.31.9 (mainline).

Wiz Research and Xint found both HTTP/2 bugs. Rapid7 and Ikotas Labs also found CVE-2026-123007, and Metnir and Palo Alto Networks Unit 42 also found CVE-2026-123633. CVE-2026-123007 has been in NGINX since HTTP/2 support first shipped in 1.9.5, in 2015. CVE-2026-123633 arrived in 1.19.7.

Xint chained CVE-2026-123007 with a separate Linux kernel flaw in SCTP to get root on the host, including from inside a Docker container. Wiz and Xint both report working exploits in their labs, and Rapid7 has published a proof of concept for CVE-2026-123007. As of disclosure, Wiz reported no confirmed exploitation in the wild.

Why does nginx2root hit Ingress NGINX so hard?

Because the default configuration is exactly what both HTTP/2 bugs need.

CVE-2026-123007 needs HTTP/2 enabled. CVE-2026-123633 needs HTTP/2 plus requests proxied to a backend.

The Ingress NGINX controller enables HTTP/2 by default (use-http2: "true"), terminates TLS, and proxies every request to a backend Service. That is the whole job.

It also usually sits at the edge of the cluster, behind a public load balancer, and every pod on a node shares that node's kernel. Wiz notes that widespread attacks tend to start with packaged products, where many customers run the same build and the same configuration. Ingress NGINX fits that description.

What does NES for Ingress NGINX fix?

NES for Ingress NGINX builds NGINX 1.27.1 from source on Alpine 3.24.0, with HeroDevs security fixes applied on top. NGINX 1.27.1 is in the affected range for both HTTP/2 CVEs.

Upstream fixes target the 1.30 and 1.31 lines. HeroDevs applied and tested four of the five upstream fixes to 1.27.1 and shipped the release.

Every NES for Ingress NGINX release lists each CVE it fixes, the patch, and whether the CVE is reachable in the controller's default configuration, with a VEX statement for each. For nginx2root:

  • CVE-2026-123007: fixed. Reachable without authentication, through HTTP/2 WINDOW_UPDATE frames and stream resets.
  • CVE-2026-123633: fixed. Reachable without authentication, since the controller turns HTTP/2 on for TLS servers and a client can use up worker_connections.
  • CVE-2026-123634: fixed. Reachable when an Ingress uses external authentication, since auth-url renders proxy_pass $target in the auth_request location, so the hostname is resolved at request time in a subrequest.
  • CVE-2026-121810: fixed. Reachable only through a snippet, since HTTP/3 is compiled in but the controller template never adds a listen ... quic socket. We applied it anyway so the QUIC code matches upstream.
  • CVE-2026-113425: not affected. The bug is in the mail proxy module, and we do not build NGINX with --with-mail, so the code is not in the binary. The release ships a not_affected VEX statement for it instead of a patch.

The same release also fixes four more NGINX CVEs from the same upstream update that are not part of nginx2root. The one that matters is CVE-2026-118899, a denial of service reachable without authentication on every TLS server. CVE-2026-123640 and CVE-2026-120967 are reachable only through a stream snippet, and CVE-2026-125283 is not reachable at all.

Full details are in the NES for Ingress NGINX release notes.

How do I upgrade NES for Ingress NGINX?

The same way as any other NES for Ingress NGINX release. Update the Helm repository and upgrade to chart [0.0.19]:

helm repo update
helm upgrade --install ingress-nginx HeroDevs/ingress-nginx \
  --version [0.0.19] \
  --namespace ingress-nginx \
  -f ingress-nginx-values.yaml

If your values file pins the controller image, change the tag:

controller:
  image:
    registry: registry.nes.herodevs.com
    image: nes/ingress-nginx
    tag: [v1.15.1-nes-1.15.12]

Then check the running image:

kubectl -n ingress-nginx get deployment ingress-nginx-controller \
  -o jsonpath='{.spec.template.spec.containers[0].image}'

On AWS Marketplace, upgrade to the new chart version listed in the product's Usage Instructions.

Each release signs the image digest in SHASUMS256.txt. The verification steps are in the Helm Charts docs.

How do I know if someone already tried to exploit nginx2root?

Upgrading closes the hole. It does not tell you whether anyone got through before you upgraded.

An attack on CVE-2026-123007 leaves almost nothing in the access log, because the HTTP/2 control frames it uses are never logged as requests. Xint suggests looking in three places:

  • Programs started by NGINX worker processes. A worker has no reason to run a shell, so this is the clearest sign of a successful attack.
  • Worker crashes. A failed attempt often crashes a worker.
  • Long-lived HTTP/2 connections from one address that keep receiving data while NGINX sends little back, often alongside many short TLS connections from the same source.

For worker crashes, the controller logs NGINX's error log to stdout:

kubectl -n ingress-nginx logs deploy/ingress-nginx-controller \
  | grep -E 'signal 11|segfault|exited on signal'

Any one of the last two can have an innocent cause. Several together, with no explanation, are worth investigating.

What about NES for NGINX?

NES for NGINX tracks the latest upstream NGINX release, so it picks up fixes for all five nginx2root CVEs with NGINX 1.31.9 in NES for NGINX. See the NES for NGINX release notes.

Frequently asked questions

Is community ingress-nginx getting a fix for nginx2root?

No. The Kubernetes project retired ingress-nginx in March 2026, and it no longer ships security releases.

Which version of NGINX is in NES for Ingress NGINX?

NGINX 1.27.1, compiled from source on Alpine 3.24.0, with HeroDevs security fixes applied. The controller is based on upstream ingress-nginx v1.15.1.

Do I need to change my Ingress resources or annotations?

No. NES for Ingress NGINX is a drop-in replacement for the upstream chart and controller image. Your Ingress resources, annotations, and values stay the same.

I disabled HTTP/2 while waiting for a fix. Can I turn it back on?

Yes, after the upgrade. Set use-http2 back to "true" in the controller ConfigMap, or just remove the key, since "true" is the default.

Will my scanner still flag the nginx2root CVEs?

It should not. The release notes and VEX statement list CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, and CVE-2026-121810 as fixed and CVE-2026-113425 as not affected, which is what auditors and VEX-aware scanners need.

Is the nginx2root fix covered by an SLA?

Yes. The NES for Ingress NGINX SLA covers CVEs in the Ingress NGINX controller and NGINX HTTP server component.

Security fixes for Ingress NGINX after end of life

If you are still running community ingress-nginx, NES for Ingress NGINX keeps the same controller, the same chart, and the same annotations, and keeps them patched. Talk to our team about coverage.

Table of Contents
Author
Hayden Barnes
Senior Open Source Partner Manager
Open Source Insights Delivered Monthly