Osegi
Security·2 min read

nginx HTTP/2 flaws allow remote code execution, F5 urges update

Two critical nginx bugs let attackers run code on a server without logging in. One has been hiding in the code since 2015, and the fix is out.

Rows of web servers in a data center with a red warning symbol over a network diagram representing a critical nginx vulnerability.
Image: ITmedia NEWS

If you run a website on nginx with HTTP/2 switched on, this is a patch not to put off. F5 said on 18 November that two nginx vulnerabilities let an attacker run code on a server remotely, with no login needed. Both are rated critical, 9.2 on the CVSS v4.0 scale.

Japan's National Cyber Directorate issued its own warning on 19 November and urged administrators to apply the update quickly.

nginx (pronounced "engine-x") is the most widely used open-source web server. It usually sits at the front of a web system, handling HTTPS traffic and passing requests on to applications and APIs. That is why a hole here matters. A successful attack could let someone run commands, steal sensitive data, tamper with a site or knock it offline.

What are the two nginx vulnerabilities?

CVE-2026-123633 is a use-after-free bug, which means memory is released and then still used. It appears when nginx forwards HTTP/2 requests to another server and the number of connections it can handle is close to the limit. Specially crafted traffic can then crash the server or run code on it.

CVE-2026-123007 is much older. It has been in nginx since version 1.9.5, released in 2015. A calculation in HTTP/2 flow control, the mechanism that regulates how much data is sent, can make nginx access memory outside its bounds. Security firm Wiz says it confirmed the attack works even on a server that only serves static files, as long as HTTP/2 is on.

Several security companies found the flaws independently and reported them to F5. Wiz says it found both with Wiz Atlas, its AI code-scanning platform, and used Gemini 4 Carbon and ChatGPT 5.6 Sol to check the impact.

How do I protect an nginx server?

F5 has released fixed versions and recommends updating. If you can't upgrade right away, Wiz suggests turning HTTP/2 off as a stopgap. Which versions and setups are affected varies, so check your own configuration.

Apps worth a look

SUMO: the number puzzle

Tap the right tiles, add them up, hit the target. Easy to learn, hard to master. Free, for all ages.

Tags:nginxf5wizhttp2vulnerabilityremote code execution

More from this day

See all →

More in: Security

See all →