DEV Community

Rohan Tech official
Rohan Tech official

Posted on Originally published at rohantechofficial.com

Two Critical Nginx Flaws Allow Unauthenticated RCE — One Has Been There Since 2015

If you run nginx with HTTP/2 enabled, stop what you are doing and check your version. Two critical flaws disclosed November 18 let an unauthenticated attacker run code on the server — and one of them has been in the code since 2015.

F5 released the fixes alongside a coordinated disclosure from Wiz Research. Five separate teams found the flaws independently: Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint. Both main flaws score 9.2 under CVSS 4.0, the critical band.

The first, CVE-2026-123007, is an integer underflow in nginx's HTTP/2 flow-control code — the mechanism that decides how much data a client may send at once. Get that accounting wrong and memory corrupts; corrupt it the right way and you get code execution. 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 proved it by achieving remote code execution, with ASLR bypassed, on a server serving nothing but static files over HTTPS. No backend, no third-party modules. The flaw sits in the protocol machinery every HTTP/2 request passes through.

The second flaw, CVE-2026-123633, is a use-after-free in HTTP/2 connection handling. It needs HTTP/2 plus a reverse-proxy setup and a worker running low on connection slots, and it has existed since nginx 1.19.7. Same 9.2 score. Behind the headlines there are five CVEs in total, including HTTP/3, DNS resolver, and mail proxy flaws, each needing its own setup. Xint chained the HTTP/2 flaw with an unpatched Linux kernel SCTP bug to go from anonymous visitor to root, and named the cluster "nginx2root."

Who is exposed? If your nginx has HTTP/2 on, you are in scope for CVE-2026-123007. One wrinkle: nginx does not enable HTTP/2 by itself — the http2 directive defaults to off. If you never turned it on, the two HTTP/2 flaws do not touch you. Also note the retired ingress-nginx controller gets no fix at all.

The fix: nginx 1.30.7 (stable) or 1.31.9 (mainline). For NGINX Plus, 37.0.8.1 and 37.3.0.1 close CVE-2026-123007; 37.0.7.1 and 37.2.0.1 close only CVE-2026-123633. Plus R34–R36 have no fix. If you cannot upgrade immediately, turn HTTP/2 off (http2 off; in server blocks on 1.25.1+, and remove the http2 parameter from listen directives). That blocks the two HTTP/2 flaws, though not the other three — a stopgap, not a fix.

Good news, for now: 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. But the flaws are public, the fixed versions are named, and scanning starts within days after every major server disclosure. Patch or disable HTTP/2 today — this is the kind of flaw where the fix takes minutes and the regret takes months.

Read the full write-up on Rohan Tech Official: https://rohantechofficial.com/tech-news/critical-nginx-flaws-remote-code-execution-patch/

Top comments (0)