ROHAN TECH OFFICIAL • Technology • AI • Apps • Tutorialsinfo@rohantechofficial.com
ROHAN TECH OFFICIALTechnology • AI • Apps • Tutorials • Digital World
Home → Tech News → Critical Nginx Flaws Let Attackers Run Code With No Login — Patch Now

Critical Nginx Flaws Let Attackers Run Code With No Login — Patch Now

By Rohan Jaspal • November 19, 2026 • Updated November 19, 2026
Critical Nginx Flaws Let Attackers Run Code With No Login — Patch Now

Two critical flaws in nginx, the web server that sits in front of a huge share of the world’s websites and APIs, let an unauthenticated attacker run code on the server. One of them has been hiding in the code since 2015. Fixes are out now, and if you run nginx with HTTP/2 enabled, this is a patch-today job.

F5 released the security updates on November 18, alongside a coordinated disclosure from Wiz Research. Five separate teams found the flaws independently — Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint — which tells you how findable these bugs were once someone looked. Both main flaws carry a CVSS 4.0 score of 9.2, the critical band.

The two flaws, in plain terms

The first flaw, CVE-2026-123007, is an integer underflow in nginx’s HTTP/2 flow-control code. Flow control is the mechanism that decides how much data a client may send at once. A mistake in that accounting corrupts memory, and a skilled attacker can turn that corruption into code execution. It is the broader of the two: it needs only one condition, HTTP/2 enabled, and it affects every official release from 1.9.5 — the version that introduced HTTP/2 in September 2015 — through 1.31.8. Ten years of releases, one bug.

Wiz Research proved the impact by achieving remote code execution, with address-space layout randomization bypassed, on a server doing nothing more exotic than serving static files over HTTPS. No backend application, no third-party modules. The flaw lives in the protocol machinery every HTTP/2 request passes through, not in some optional add-on.

The second flaw, CVE-2026-123633, is a use-after-free in HTTP/2 connection handling. It needs more conditions: HTTP/2 enabled, requests proxied to a backend, and the worker running low on connection slots. It has existed since nginx 1.19.7 and carries the same 9.2 score.

Behind the headlines, the disclosure covers five CVEs in total — the two HTTP/2 flaws plus CVE-2026-121810 (HTTP/3), CVE-2026-123634 (DNS resolver) and CVE-2026-113425 (mail proxy) — each needing its own specific setup. Xint, one of the reporting teams, chained the HTTP/2 flaw with a separate unpatched Linux kernel SCTP bug to go from an anonymous web visitor to root on the host, and gave the cluster the name “nginx2root”.

Who is actually exposed

If your nginx has HTTP/2 turned on, you are in scope for CVE-2026-123007. That sounds like almost everyone, but there is a wrinkle: nginx does not enable HTTP/2 by itself. The http2 directive defaults to off, so exposure comes from an explicit configuration choice. Many modern setups enable it for performance, which is why the flaw matters so much — but if you never turned it on, you are not affected by the two HTTP/2 flaws.

The reverse-proxy flaw, CVE-2026-123633, needs the proxy setup too. The other three flaws each need their own configuration, so check the advisory against your setup rather than assuming the worst — or the best.

One more thing worth knowing: the retired ingress-nginx controller will not get a fix. If you still run it, migration is the only answer.

How to fix it tonight

The fixed releases are nginx 1.30.7 (stable) and 1.31.9 (mainline). Both close both CVEs. For NGINX Plus, the fixed builds are 37.0.8.1 and 37.3.0.1 for CVE-2026-123007, while 37.0.7.1 and 37.2.0.1 close only CVE-2026-123633. Note that NGINX Plus R34 through R36 have no fix at all, and major Linux distributions had not shipped patched packages at the time of disclosure — check your distro’s changelog rather than trusting the version string.

If you cannot upgrade right away, Wiz’s advice is to turn HTTP/2 off: set http2 off; in the affected server blocks on nginx 1.25.1 or later, and remove the http2 parameter from any listen directives. That blocks the two HTTP/2 flaws, though not the other three — so treat it as a stopgap, not a fix.

What we still don’t know

As of November 18, no exploitation in the wild has been publicly reported, and none of the five CVEs is in CISA’s Known Exploited Vulnerabilities catalog. Wiz is not releasing its exploits. Rapid7 has published a proof of concept for CVE-2026-123007, but it needs roughly 128 GB of HTTP/2 traffic and a specific glibc memory-copy implementation, so it is not a weapon anyone can fire casually.

That calm will not last. The flaws are now public, the fixed versions are named, and attackers can work out which servers have not patched yet. The pattern after every major server disclosure is the same: scanning starts within days. The Optimizely compromise this week showed how fast one flaw in shared infrastructure spreads, and the AI hacking framework Google documented shows how quickly flaws now become working exploits.

Check your nginx version, check whether HTTP/2 is on, and patch or disable it. This is the kind of flaw where the fix takes minutes and the regret takes months.