Blog/Engineering
Engineering

nginx2root: Five nginx Flaws Including HTTP/2 RCE CVE-2026-123007 Fixed in 1.30.7 and 1.31.9. Which Configs Are Affected and a Fix Checklist for Gulf and Egypt Teams

D
DanteNov 21, 2026 · 6 min read
iFynx original graphic: nginx2root, five nginx CVEs fixed in 1.30.7 and 1.31.9

CRITICAL PATCH · NGINX · NGINX2ROOT · CHECKED 09:00 ASIA/GAZA, 21 NOV 2026

Update nginx to 1.30.7 or 1.31.9 now. On 18 November 2026 nginx fixed five memory-safety flaws, nicknamed nginx2root, the worst of which (CVE-2026-123007) can let a remote attacker run code on servers with HTTP/2 enabled. No attacks are reported yet, but the researchers say they have working exploits.

Primary sources: nginx.org security advisories and the Xint research write-up. A reload is not enough: restart nginx fully after upgrading.

iFynx original graphic: nginx2root, five nginx CVEs fixed in 1.30.7 and 1.31.9, with the HTTP/2 flaw CVE-2026-123007, for Gulf and Egypt web teams
Original iFynx illustration.

At iFynx we build and run websites, APIs and platforms for banks, fintechs, retailers and government-facing teams in the UAE, Saudi Arabia, Egypt and Palestine, and nginx sits in front of most of them. It is likely in your stack too, even if nobody on the team installed it on purpose: in Kubernetes ingress, API gateways and container images. Here is what was fixed, which settings matter, and the order to fix things in.

Which nginx versions are affected by nginx2root?

All five bugs are fixed in nginx 1.30.7 (stable) and 1.31.9 (mainline), both released on 18 November 2026, according to nginx.org. Each bug only matters if a specific feature is switched on, so the table below shows what each needs.

CVE What it is nginx severity Needs Vulnerable versions
CVE-2026-123007 Memory corruption in HTTP/2 flow control major HTTP/2 enabled 1.9.5 to 1.31.8
CVE-2026-113425 Use-after-free in the mail proxy module major mail proxy with auth_http 0.5.33 to 1.31.8
CVE-2026-123633 Use-after-free in HTTP/2 medium HTTP/2 + requests sent to an upstream 1.19.7 to 1.31.8
CVE-2026-121810 Use-after-free in HTTP/3 medium HTTP/3 (QUIC) + upstream 1.25.0 to 1.31.8
CVE-2026-123634 Use-after-free in the resolver medium resolver + variable proxy_pass + mirror 0.6.18 to 1.31.8

STABLE

1.30.7

Released 18 Nov 2026

MAINLINE

1.31.9

Released 18 Nov 2026

DISTRO PACKAGES

Check the notice

The fix may be backported under an older version number

Security Affairs reports that all five have a CVSS 4.0 score of 9.2 and that NGINX Plus is fixed in 37.3.0.1 and 37.0.8.1. We could not read F5’s advisory pages to confirm those two points, so treat them as reported, not confirmed. Which CVSS number applies matters less than the fact that the fix is out.

How bad is CVE-2026-123007, and what does “to root” mean?

CVE-2026-123007 is a memory corruption bug in how nginx keeps track of HTTP/2 flow control. Xint says it can be triggered remotely without a login on servers with HTTP/2 on, and can lead to code running as the nginx worker process. That user normally has limited rights. The “root” part came from chaining it with a separate Linux kernel flaw, which in the researchers’ demos also escaped a Docker container. We describe this only at a high level; no attack steps here.

Remote request

HTTP/2 traffic hits a vulnerable nginx

→

nginx worker

Code runs as the worker user (CVE-2026-123007)

→

Kernel flaw

A separate Linux bug turns that into root

Source: Xint. The kernel flaw is separate from nginx; patching either breaks this chain, patching both is the goal.

Is anyone exploiting this? As of 21 November 2026 we found no report of attacks, and CVE-2026-123007 was not on CISA’s KEV list when Security Affairs checked. But the researchers published videos of working exploits on AWS, Google Cloud, Azure and bare metal, and nginx runs a huge share of the web. Expect attackers to try.

nginx2root fix checklist for Gulf and Egypt teams

Do these in order

1
Find every nginx. Web servers, reverse proxies, Kubernetes ingress controllers, API gateways, Docker images and appliances that bundle nginx. Note the version and whether HTTP/2, HTTP/3 or the mail proxy is on.
2
Upgrade. Move to nginx 1.30.7 (stable) or 1.31.9 (mainline), both released on 18 November 2026. If you use your Linux distribution’s package, follow its security notice instead: distributions often backport the fix without changing the version that nginx -v prints.
3
Restart, don’t just reload. A reload keeps the old binary running. Do a full restart after upgrading, and rebuild container images rather than only pulling new base images on running hosts.
4
If you cannot upgrade today: for CVE-2026-123007 and CVE-2026-123633, turning HTTP/2 off on exposed listeners removes the main risk (http2 off; on 1.25.1+, or remove http2 from listen). This does not cover the HTTP/3, resolver or mail-proxy bugs: switch off QUIC listeners you don’t need, avoid request-time DNS in proxy_pass, and limit the mail proxy to trusted networks.
5
Patch the kernel too. The researchers reached root only by chaining nginx with a separate Linux kernel flaw. Keep kernels on your distribution’s latest security release, and don’t run nginx as root or in privileged containers.
6
Watch. Look for nginx worker crashes or restarts, unusual HTTP/2 traffic and unexpected child processes of nginx workers. Repeated worker crashes after 18 November deserve a closer look.

Why this matters in the UAE, Saudi Arabia and Egypt

Bank portals, payment gateways, e-commerce sites and government e-services in the region are commonly served through nginx, often inside Kubernetes ingress controllers or vendor appliances that teams forget to update. Two traps we see often: sites behind Cloudflare or another CDN assume they are covered, but the origin nginx still runs the vulnerable code; and container images keep an old nginx long after the host is patched. This is the second HTTP/2 server flaw this week after Apache HTTP Server CVE-2026-119618: exploited mod_http2 RCE, so check both web servers together.

How iFynx can help

iFynx builds and runs bilingual (Arabic and English) web platforms for the UAE, Saudi Arabia, Egypt and Palestine. We can:

  • Find every nginx in your servers, containers and Kubernetes ingress
  • Plan and run the upgrade and full restart with minimal downtime
  • Harden nginx and kernel settings, and set up alerts for worker crashes

Contact iFynx · Our services

💰 Estimate your project cost with iFynx in one minute

Frequently asked questions

What is nginx2root?

nginx2root is the name researchers at Xint gave to five memory-safety flaws in nginx, fixed on 18 November 2026: CVE-2026-123007, CVE-2026-113425, CVE-2026-123633, CVE-2026-121810 and CVE-2026-123634. nginx rates two of them major and three medium. The name comes from the researchers’ demo that chained one of them with a Linux kernel flaw to get root.

Which nginx version fixes nginx2root?

nginx 1.30.7 (stable) and 1.31.9 (mainline), released on 18 November 2026, fix all five. Distribution packages may carry the fix under an older version number, so check your distribution’s security notice.

Is my server vulnerable if I don’t use HTTP/2?

Possibly not to the most serious bug, CVE-2026-123007, which needs HTTP/2. But the other four depend on HTTP/3, the mail proxy or certain resolver and mirror setups, so check each one against your configuration, or simply upgrade.

Are these flaws exploited in the wild?

As of 21 November 2026, we found no report of attacks, and Security Affairs reported that CVE-2026-123007 was not in CISA’s Known Exploited Vulnerabilities catalog when it wrote its story. The researchers say they have working exploits but deliberately left out the final steps. With the patch public, that can change quickly.

Do sites behind Cloudflare or a CDN still need to patch?

Yes. A CDN in front changes which traffic reaches your server, but the origin nginx still runs the vulnerable code, and many internal services and ingress controllers are reachable without the CDN. Patch the origin.

How can iFynx help?

iFynx builds and runs web platforms for teams in the UAE, Saudi Arabia, Egypt and Palestine. We can find every nginx instance in your stack, plan a safe upgrade and restart, and harden the configuration.

Sources

Related reading

🛡️ iFynx security bulletin · every SundayThe week’s vulnerabilities that matter to Gulf and Egypt companies, in one email

Every Sunday: the most serious confirmed CVEs and breaches, who is exposed in Saudi Arabia, the UAE and Egypt, and what to patch first. Free, in English and Arabic, one-click unsubscribe.

Read past issues →