Skip to content
← All stories

Vulnerabilities · Application Security

Critical NGINX2Root flaws patched in NGINX web server

F5 has released patches for five critical NGINX vulnerabilities, dubbed 'NGINX2Root', that could let attackers take control of affected servers. Security teams should update NGINX as soon as possible.

Ross Grant3 min read

Laptop installing a security update

The short version

F5 has fixed five severe bugs in NGINX, a popular web server used worldwide. These flaws could let attackers take control of servers if not patched. Security experts say millions of servers could be at risk. If you run NGINX, check your version and update it right away.

By the numbers

  • 5critical NGINX vulnerabilities patchedSophos
  • 9 millionNGINX services exposed with HTTP/2 enabledSecurityWeek
  • 9.2CVSS v4.0 severity score for each flawSophos
  • 128 GBamount of HTTP/2 data needed for one PoC exploitSecurityWeek

What happened?

F5 has released patches for five critical vulnerabilities in NGINX, known as 'NGINX2Root'. The flaws could let attackers crash servers or run code remotely. Proof-of-concept exploits have been published, but there are no reports of attacks in the wild. Security teams are urged to update NGINX as soon as possible.

How the flaw works

F5 has released patches for five critical vulnerabilities in NGINX, a widely used web server and reverse proxy. Security researchers have named these flaws 'NGINX2Root'. Each has a CVSS v4.0 score of 9.2, which means they are considered very severe. The vulnerabilities affect both NGINX Open Source and NGINX Plus. If exploited, they could let attackers crash the server, cause denial of service, corrupt memory, or in some cases, run their own code on the server (Sophos (opens in a new tab), SecurityWeek (opens in a new tab)).

Two of the flaws relate to how NGINX handles HTTP/2 traffic. One is an integer underflow issue (CVE-2026-123007), and the other is a use-after-free bug (CVE-2026-123633). Both can be exploited if HTTP/2 is enabled. The other three issues are also use-after-free bugs, but they require specific configurations, such as using NGINX as a mail proxy or with certain proxy settings.

Who is affected

These vulnerabilities affect NGINX Open Source and NGINX Plus servers, including those running in Docker containers. According to Censys, about 9 million NGINX services on the internet are running an affected version with HTTP/2 enabled. Another 103 million services do not reveal their version, so the true number at risk could be higher.

How the attack worked

Attackers could exploit these flaws remotely, without needing to log in. For some vulnerabilities, successful exploitation could let them run code as the nginx worker process, which could lead to full server compromise. In lab tests, researchers showed that chaining these flaws with a separate Linux kernel vulnerability could let attackers gain root access to the host, even when NGINX is running inside a Docker container.

One proof-of-concept (PoC) exploit for CVE-2026-123007 requires sending a large amount of HTTP/2 traffic (about 128 GB) to trigger remote code execution, which could take from two minutes to an hour depending on network speed. However, other researchers have shown that it may be possible to exploit the flaw with less traffic in some setups.

The response

F5 has released patches for the affected versions: NGINX Open Source 1.30.7 and 1.31.9, and NGINX Plus 37.0.8.1 and 37.3.0.1. Updated packages are available from the NGINX website, but may not be ready for older, unsupported Linux distributions. After updating, administrators must restart NGINX or upgrade its binary, as a simple reload does not apply the fix.

If immediate patching is not possible, F5 and researchers recommend disabling HTTP/2, avoiding certain proxy configurations, and restricting mail proxy listeners to trusted networks. There is no evidence yet that these flaws have been exploited in the wild.

What you should do

Administrators running NGINX should check their version and apply the latest patches as soon as possible. If you cannot patch right away, follow the temporary workarounds suggested by F5 and researchers. Monitor for updates from F5 and security advisories for any signs of active exploitation.

Why it matters

NGINX is one of the most widely used web servers, powering millions of websites and services. Critical flaws like these can put large numbers of systems at risk of being taken over by attackers. Prompt patching is essential to prevent possible breaches.

Key points

  1. Five critical NGINX vulnerabilities have been patched by F5.
  2. The flaws could allow remote code execution or server crashes.
  3. About 9 million NGINX services may be exposed with HTTP/2 enabled.
  4. Proof-of-concept exploits are public, but no attacks have been reported yet.
  5. Admins should patch NGINX or apply workarounds immediately.

Sources

  1. Sophos

    Reference

  2. SecurityWeek

    Reference

The day's cyber news in 5 minutes.

Cyberend Daily is one short email with the stories that matter, written so anyone can follow.

Includes our free beginner roadmap · No spam · Unsubscribe anytime