Osegi
Security·2 min read

Nginx vulnerability lets attackers run code on a server with no login

Two critical Nginx flaws in HTTP/2 handling allow remote code execution without a password, even on a server that only serves static files. One bug dates to 2015.

A server rack in a dark data center with a red warning symbol glowing over the screen of a web server console.
Image: 3DNews - Daily Digital Digest

If your website runs on Nginx, it is worth checking which version you have today. Researchers have found two critical Nginx vulnerabilities that let an attacker run code on the server remotely, with no login and no help from a bug in your own site.

The flaws were found independently by teams at Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint. Both sit in the way Nginx handles HTTP/2, and both scored 9.2 on the CVSS 4.0 scale, which tops out at 10. They are tracked as CVE-2026-123633 and CVE-2026-123007.

What are the Nginx flaws?

CVE-2026-123633 is a use-after-free bug. The server frees a chunk of memory while it is still being used to process a request. CVE-2026-123007 is an integer overflow in the way HTTP/2 data flow is managed, which leads to incorrect memory operations.

The second one has been in the code since Nginx 1.9.5, released in 2015. That is more than ten years unnoticed.

What makes this nasty is that the problem is in Nginx itself. The researchers confirmed code execution even on a server that only hands out static files, with no extra modules and no application behind it. A successful attacker could steal confidential data, change what a site shows or knock services offline.

Wiz Research used its own platform, Wiz Atlas, to find the bugs, and used Gemini 4 Carbon and ChatGPT 5.6 Sol to check what exploitation would actually do. The team built working test exploits but says it does not plan to publish them for now.

How do I fix it?

F5, the company behind Nginx, has released patches. For Nginx Open Source, both bugs are fixed in versions 1.30.7 and 1.31.9. For Nginx Plus, the fixed builds are 37.0.7.1 and 37.2.0.1 for CVE-2026-123633, and 37.0.8.1 and 37.3.0.1 for CVE-2026-123007.

If you run Nginx for sites, web apps or APIs, updating to one of those versions is the step that matters.

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:nginxvulnerabilityhttp/2f5wiz researchcve

More from this day

See all →