⚡ Two NGINX flaws let attackers in without a password

⚡ Eleven years. That’s how long one of these two bugs lived in NGINX, the software that receives a request before a website or API sees it. On November 18, 2026, fixes shipped for CVE-2026-123007 and CVE-2026-123633. Both flaws are in HTTP/2. In the lab, researchers ran code on a server without an account.

The number that caught my eye was 225 million. Wiz estimates that’s how many websites NGINX serves. It’s a measure of the software’s reach. The risk to any given site depends on its version, its patches and whether NGINX accepts HTTP/2.

Two bugs in one protocol

HTTP/2 lets a browser exchange data for several requests over a single connection. NGINX has to track how much data it can send and which parts of a request are still in memory. Both mechanisms had a bug.

AdvisoryWhat went wrongWhere it matters
CVE-2026-123007A flow-control counter exceeds its limit. A write can run past the end of allocated memory.HTTP/2 is enabled. The bug dates back to NGINX 1.9.5, released in 2015.
CVE-2026-123633A worker tries to use memory that has already been freed.NGINX proxies HTTP/2 requests and the worker runs low on available connections. The bug dates back to 1.19.7.

I wouldn’t shrug off a worker crash. A visitor sees a dropped request. An attacker may be able to turn the same memory bug into code execution. Wiz confirmed code execution with an ASLR bypass on official builds 1.31.7 and 1.31.8. ASLR is a defense that makes memory addresses harder to predict.

How the researchers reached root in the lab

Xint demonstrated how access as an NGINX worker inside a Docker container could lead to root access on the Linux host. That second step relied on a separate kernel flaw. The potential damage depends on which files, keys and internal services the compromised process can reach, and how those components are isolated.

Wiz says five teams found the HTTP/2 flaws independently. Researchers used AI to help find bugs, then verified code execution on a running server. That’s the part I paid closest attention to.

What to do now

  1. Update NGINX Open Source to 1.30.7 stable or 1.31.9 mainline. For NGINX Plus, use 37.0.8.1 LTS, 37.3.0.1 CR or a later patched release. If you install through a Linux distribution, check its advisory. Distributions can backport a fix to an older branch.
  2. If you can’t patch immediately, temporarily disable HTTP/2 on exposed listeners. Test the configuration and make sure the old workers exit. This mitigates the two HTTP/2 flaws. The November release fixes other NGINX issues as well.
  3. After updating, verify the running process version, HTTPS and application responses. If you run NGINX in a container, check for host kernel updates separately.

I’d start with internet-facing proxies. Seeing the updated package on disk is only half the job. Make sure the patched process is already serving traffic.

Sources. NGINX security advisories · Wiz Research’s analysis · Xint’s NGINX2Root report.

—0

Loading comments...

More magazine