Technology

Why New Critical NGINX Flaws Put Millions of Sites at Risk

Security researchers have uncovered two critical remote code execution vulnerabilities in NGINX, impacting millions of websites worldwide.

WhyThisBuzz DeskNov 19, 20262 min read
Share:

Security researchers have uncovered two critical remote code execution (RCE) vulnerabilities affecting NGINX, the world's most widely used open-source web server. Powering more than 225 million websites, NGINX often acts as the primary front door for modern web architectures, handling HTTPS and routing incoming traffic to essential APIs and applications.

Tracked as CVE-2026-123633 and CVE-2026-123007, both flaws carry a severe CVSS score of 9.2. Because the weaknesses reside within NGINX itself, organizations can be exposed even if their underlying application code is completely secure.

What Happened

The vulnerabilities stem from memory-safety issues in how NGINX handles HTTP/2 traffic. CVE-2026-123633 is a use-after-free flaw tied to reverse-proxy processing when available connection slots run low. Meanwhile, CVE-2026-123007 involves incorrect flow-control accounting that leads to an invalid memory copy.

Both flaws require HTTP/2 to be enabled on the target server. In testing, researchers successfully demonstrated unauthenticated remote code execution on NGINX servers serving ordinary static files—requiring no backend application or third-party modules.

Notably, one of the flaws had remained hidden in the codebase since 2015, while the other had been present for nearly six years. Researchers noted that advanced AI tools played a major role in tracing these subtle, complex memory interactions to uncover the longstanding defects.

Why It Matters

Successful exploitation allows unauthenticated attackers to execute arbitrary code on the server, steal sensitive data, tamper with websites, or completely disrupt services. Because a single NGINX deployment frequently routes traffic for multiple distinct applications, a compromise can instantly put an entire network of digital services at risk.

F5, the company behind NGINX, worked in coordination with security researchers to investigate the findings and release official patches.

What You Should Do

Administrators and security teams should immediately audit their infrastructure to identify affected NGINX deployments.

  • Apply Patches: Upgrade affected NGINX instances to the latest security release provided by F5 as soon as possible.
  • Temporary Workaround: If immediate upgrading is not feasible, temporarily disable HTTP/2 on vulnerable instances by setting http2 off; in affected server blocks and removing the http2 parameter from listen directives.

As threat actors look to weaponize complex memory-safety flaws, prompt patch management remains the most critical line of defense for production environments.