Nov 28, Paris: AI Health Hack #2 with Alan, Qovery and AWS. Applications close Nov 21

NGINX2Root: remote code execution in nginx

On 18 November 2026, Xint and Wiz disclosed NGINX2Root, a set of vulnerabilities in nginx. The most serious one lets an unauthenticated attacker run code on nginx through HTTP/2. Envoy Gateway is not affected. Clusters where the legacy NGINX ingress controller is still installed are, even if all their traffic already goes through Envoy, because NGINX keeps its own public load balancer. The fix is to remove NGINX.

Disclosed
November 18, 2026
Status
Action required on some clusters
Severity
Critical
Component
Legacy NGINX ingress controller

Who is affected

  • Qovery clusters where the legacy NGINX ingress controller is still installed, that is where the cluster advanced setting k8s.remove_nginx is not set to true.
  • This includes clusters that already serve all their traffic through Envoy Gateway. NGINX stays reachable on its own load balancer until it is removed.

Not affected

  • Clusters where k8s.remove_nginx is true and the cluster has been redeployed since. NGINX and its load balancer are gone.
  • Traffic served by Envoy Gateway, the default ingress on Qovery clusters since 2026.

What we did (UTC)

  1. 18 NovXint and Wiz publish NGINX2Root.
  2. 18 Nov, 18:57Our team confirms that the NGINX build we shipped (ingress-nginx controller 1.13, with HTTP/2 on) is in the affected range. The ingress-nginx project was archived in March 2026, so no patched controller release is coming.
  3. 18 Nov, 19:38We list every customer cluster where NGINX is still installed, across all organizations.
  4. 19 Nov, 07:35Each affected team receives a message in its shared Slack channel naming its clusters, explaining the fix and what it changes, and offering to check the clusters or do the change with them.
  5. 19 NovOur engineers start checking clusters for the teams that asked, then remove NGINX with them.

What to do

  1. Open the cluster advanced settings in the Console and check that k8s.use_api_gateway is true and that every public service has been redeployed since. If not, follow the NGINX to Envoy migration guide first.
  2. Check that every custom domain points to the target shown for it in the Console, not to the old NGINX load balancer.
  3. If a service uses network.ingress.* advanced settings, set the network.gateway_api.* equivalent and redeploy the service.
  4. Set k8s.remove_nginx to true and redeploy the cluster. On clusters with several environments, start with staging.
  5. Check that your domains still answer and that the NGINX load balancer is gone from your cloud account.

What changes once NGINX is removed

  • On the next cluster deployment, Qovery uninstalls the NGINX ingress controller and deletes its load balancer. Anything still sending traffic to that load balancer stops getting answers.
  • Services that already go through Envoy keep running with no downtime. Their NGINX Ingress objects are removed the next time each service is deployed.
  • NGINX-only service settings (network.ingress.*) stop applying. Envoy uses the network.gateway_api.* settings instead.
  • Some defaults NGINX added are not added by Envoy. NGINX sent an HSTS header on every response; you can add it back per service with network.gateway_api.add_headers.
  • Your cloud bill drops by one load balancer per cluster.
  • The change can be undone: set k8s.remove_nginx back to false and redeploy the cluster.

Vulnerabilities

CVE-2026-123007

CVSS 9.2

Integer underflow in HTTP/2 flow control. An unauthenticated attacker can run code on any nginx from 1.9.5 to 1.31.8 that accepts HTTP/2.

CVE-2026-123633

CVSS 9.2

Use-after-free on HTTP/2 connections that forward requests to a backend, nginx 1.19.7 to 1.31.8.

CVE-2026-121810

Affects HTTP/3 listeners that forward requests to a backend. Qovery does not enable HTTP/3 on NGINX.

CVE-2026-123634

Needs a resolver, a variable proxy_pass destination and mirror. Not part of the configuration Qovery generates.

CVE-2026-113425

Affects the nginx mail proxy. Qovery does not use it.

Questions

All my services run on Envoy. Am I affected?

Only if NGINX is still installed on the cluster. Moving services to Envoy does not remove NGINX on its own; the k8s.remove_nginx setting does. If you are unsure, ask us in your shared channel and we will check your clusters.

Is there a patched NGINX version we could upgrade to instead?

nginx itself is fixed in 1.30.7 and 1.31.9, but the Kubernetes ingress-nginx project was archived in March 2026 and does not ship new releases. Removing NGINX is the fix we support.

Has this been exploited?

As of 19 November 2026, no public exploit or attack has been reported. The researchers have not released their exploits.

Can Qovery do the change for us?

Yes. Reply in your shared Slack or Microsoft Teams channel, or open a ticket. We check the cluster first and agree on a time for the redeploy with you.

References

Last updated November 19, 2026

Ask us to check your clusters