Now Nginx Has Critical Vulnerabilities

nginx is an open source web server and reverse proxy that sits in front of apps and passes traffic to them, and it is one of the most widely used web servers around.
That kind of broad implementation is why a set of ten vulnerabilities fixed in nginx 1.30.7 and 1.31.9 are significant; five of them even let attackers run code on a server.
The stable branch gets its fix in 1.30.7 and mainline gets it in 1.31.9; both went out yesterday.
Plus, most of the five only matter if a specific feature is in use. As a sysadmin, the first job you need to do is work out which ones match what your servers run.
The vulnerabilities
Each is a separate bug in a different part of nginx. nginx rates two of them as major and three as medium.
Its changelog says two of them might crash a worker process or have other impacts, with F5, the company that owns nginx, saying an attacker could run code under certain conditions.
F5 gives all five a 9.2 Critical score on CVSS 4.0. ๐
Two of them are in HTTP/2. CVE-2026-123007 is a memory bug in HTTP/2 flow control that goes back to nginx 1.9.5 and is rated major. If you didn’t know, flow control limits how much data a server sends at once.
CVE-2026-123633 is a use-after-free. That means the code keeps using memory after it has been released. It can happen in a worker process when HTTP/2 is in use and worker_connections is not enough. It is rated medium.
CVE-2026-121810 is the HTTP/3 one. It is another use-after-free with the same worker_connections condition, and it is rated medium. The affected range reaches back to nginx 1.25.0.
CVE-2026-123634 sits in the resolver and is also a use-after-free rated medium. It can happen when the resolver directive is in use and the same name is resolved at the same time in subrequests.
CVE-2026-113425 affects the mail proxy and only matters if you run nginx as one. It is rated major and has the oldest affected range of the five, starting at nginx 0.5.33.
F5’s CVE records list NGINX Plus as affected too.
Protect your systems
The fix is to update to 1.31.9 if you follow mainline, or to 1.30.7 if you follow stable. Both are available from nginx.org.
The same releases also fix five other vulnerabilities, including an infinite loop while reading request bodies over TLS 1.3 that nginx rates as major.
Suggested Read ๐: Canonical is now shipping AI-written security patches to Ubuntu Pro users.
![]()
