Read-only POSIX sh audit for the five NGINX2Root nginx CVEs (HTTP/2, HTTP/3, resolver, mail proxy), judged per CVE
Read-only audit for the five NGINX2Root memory-safety flaws: two in HTTP/2
(CVE-2026-123007, CVE-2026-123633), one in HTTP/3 (CVE-2026-121810),
one in the resolver (CVE-2026-123634) and one in the mail proxy
(CVE-2026-113425). All five were fixed together on 2026-11-18 in nginx
1.30.7 (stable) and 1.31.9 (mainline). Before version 1.2.0 this script
covered only the first two and called an instance MITIGATED as soon as HTTP/2
was not reachable. That is wrong as a general statement: switching HTTP/2 off
does not stop the HTTP/3, resolver and mail bugs.
The repository and the script keep the name cve-2026-123633-123007-nginx-audit
for continuity; the name still lists only the first two CVEs.
Written in POSIX sh, so it runs as is on busybox ash (Alpine, Synology),
on dash and on bash. It never sends a request, never runs an exploit and never
changes anything on the host.
It finds every nginx on the machine (running and merely installed, containers included when their processes are visible), reads the version of the binary that really runs, reads the effective configuration, decides per CVE whether the version is affected and whether the bug is reachable, and looks for signs of attempts.
All five exist up to 1.31.8 and are fixed in 1.30.7 and 1.31.9. The first affected version below is the one on the nginx.org security advisories page, which is the authority used here.
| CVE | Bug | First affected | nginx.org severity | Reachable when |
|---|---|---|---|---|
| CVE-2026-123007 | HTTP/2 flow-control integer underflow (send_window) | 1.9.5 | major | HTTP/2 on a reachable listener. Works against plain static file serving over TLS |
| CVE-2026-123633 | HTTP/2 use-after-free (failed GOAWAY allocation) | 1.19.7 | medium | HTTP/2 on a reachable listener. More likely in reverse-proxy setups |
| CVE-2026-121810 | HTTP/3 (QUIC) use-after-free | 1.25.0 | medium | a listen ... quic on a non-loopback address in a server whose http3 is not off, AND requests proxied upstream (proxy_pass, grpc_pass, fastcgi_pass, uwsgi_pass, scgi_pass) |
| CVE-2026-123634 | resolver use-after-free | 0.6.18 | medium | resolver AND a proxy_pass whose host part contains a variable AND an SSI (ssi on) or mirror subrequest that resolves the same name |
| CVE-2026-113425 | mail proxy use-after-free | 0.5.33 | major | a top-level mail {} block with proxy on and auth_http, and a mail listener on a non-loopback address |
Where the sources disagree. For 123634 nginx.org says 0.6.18, while the
Xint write-up only tested from 1.13.4: the script uses 0.6.18. For 113425
nginx.org says 0.5.33, while some lists say 0.5.15: the script uses 0.5.33.
A version between two first-affected versions is affected only by the bugs whose
first affected version is at or below it (1.8.1: the resolver and mail bugs; 1.22.1:
everything but HTTP/3; 1.25.0 and later: all five). An instance is NOT_APPLICABLE
only below 0.5.33.
How serious. Wiz scores the HTTP/2 pair CVSS 4.0 9.2 (critical); the nginx.org list rates them "major" (123007) and "medium" (123633). Wiz says a working HTTP/2 exploit needs a memory disclosure first and heap grooming; Rapid7 says 123007 needs about 128 GB of HTTP/2 traffic on one connection. Treat all five as demanding but realistic attacks, and patch. NGINX Plus is fixed in 37.0.8.1 / 37.3.0.1 (123007) and 37.0.7.1 / 37.2.0.1 (123633); see the F5 advisories K000163925, K000163926, K000163927, K000163928 and K000163931.
# review it first, then run as root (nginx -T and the error logs need root)
sh cve-2026-123633-123007-nginx-audit.sh
sh cve-2026-123633-123007-nginx-audit.sh --json
sh cve-2026-123633-123007-nginx-audit.sh --quiet # verdict only
sh cve-2026-123633-123007-nginx-audit.sh --no-hunt # skip logs and process hunt
sh cve-2026-123633-123007-nginx-audit.sh --no-banner # text report without the banner
On a remote host, nothing is copied to disk:
ssh host 'sh -s' < cve-2026-123633-123007-nginx-audit.sh
ssh host 'sh -s -- --json' < cve-2026-123633-123007-nginx-audit.sh
Without root the script still runs, but it cannot read other users' /proc
entries, run nginx -T or read the error logs. The result is then UNKNOWN
unless the build is already fixed. The banner is printed only in the text report;
--quiet and --json never print it.
| exit | verdict | meaning |
|---|---|---|
| 0 | PATCHED | every instance runs a fixed build |
| 0 | NOT_APPLICABLE | no nginx, OpenResty, Angie or Tengine here, or the version predates all five bugs (below 0.5.33) |
| 1 | MITIGATED | unfixed code, but none of the five bugs is reachable right now. Still patch |
| 2 | VULNERABLE | unfixed code and at least one of the five bugs is reachable, or indicators of compromise found |
| 3 | UNKNOWN | cannot decide (not root, a distribution build, an unreadable process). Treat as suspect |
| 4 | usage error or missing basic tools |
With several instances the worst one wins. A running process whose binary
path cannot be read (no root) lowers the result to at least UNKNOWN.