Critical NGINX Vulnerabilities Found in Major Web Server

Massive vulnerabilities have been discovered in NGINX, the open-source web server powering a third of all websites.

What Happened

Researchers at Xint found at least 10 bugs in NGINX, including critical flaws in its HTTP/2 support. These vulnerabilities span multiple versions and have existed since NGINX introduced HTTP/2 in 2015 — over a decade ago.

One of the most severe flaws, CVE-2026-123007, is nicknamed ‘nginx2root.’ It allows attackers to run code on an NGINX server without logging in. No credentials are needed.

Attackers could steal data, inject malware, or disrupt services using just a specially crafted HTTP/2 request.

Key Vulnerabilities

AI tools helped detect these issues. In 2025, NGINX’s security list had only two new vulnerabilities. This week, it recorded 26 — not counting ‘nginx2root.’

Why It Matters

NGINX powers about one-third of all websites. That means nearly every major site — from e-commerce to social media — runs on it.

Security experts have long believed unauthenticated code execution in NGINX was nearly impossible. Its long history of audits makes this flaw especially surprising.

Without authentication, attackers can access server data, inject scripts, or launch denial-of-service attacks — all without passwords.

How the Flaws Work

Both CVE-2026-123633 and CVE-2026-123007 stem from memory handling in HTTP/2 connections.

In CVE-2026-123633, memory is freed before the request finishes. This creates a ‘use-after-free’ condition that can be exploited.

In CVE-2026-123007, incorrect flow-control accounting leads to invalid memory copies. This allows attackers to manipulate data flow and trigger memory corruption.

These flaws operate at a deep level. They are hard to detect with standard tools and require specialized analysis to spot.

Massive vulnerabilities found in NGINX, open-source server powering a third of all websites. Via original publisher. · Source

What Admins Should Do

  1. Update immediately: Install NGINX 1.31.9 as soon as possible. A config reload is not enough. The running process must be restarted.
  2. If update isn’t possible: Disable HTTP/2 on all affected listeners. This stops exploitation of the unauthenticated RCE flaw.

F5, the company behind NGINX, issued an out-of-band security alert. It warns that while no attacks have been reported, the risk is high and the window to act is narrow.

Background: How NGINX Works

NGINX is an open-source web server built for performance and scalability. It handles many concurrent connections efficiently — ideal for high-traffic sites.

However, these performance features introduced deep flaws in memory and connection management.

Limitations and Open Questions

No confirmed attacks have been reported yet. The threat remains theoretical — but the impact could be massive.

It’s unclear how many websites are currently exposed. Organizations must audit their systems to assess risk.

These flaws show that even trusted systems need constant, rigorous testing.

AI-assisted research played a key role. AI tools analyzed millions of code lines to find patterns invisible to human researchers.

What to Watch Next

Security teams should monitor for signs of exploitation. If attackers begin targeting NGINX sites, widespread outages or data breaches could follow.

Admins must verify their configurations. If updates are delayed, disable HTTP/2. Regular patching and reviews are essential for safe web operations.

For more on similar server-level flaws, see a recent report on UEFI firmware flaws.

For full technical details, refer to the original source at Cybernews.

Sources & further reading

Featured image: Massive vulnerabilities found in NGINX, open-source server powering a third of all websites. Via original publisher. Image source

Exit mobile version