Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Product Based Web Vulnerabilities·Updated Nov 18, 2026

NGINX2Shell (CVE-2026-123007 & CVE-2026-123633) Scanner

NGINX2Shell potential checker for the nginx HTTP/2 remote code execution (CVE-2026-123007) and use-after-free (CVE-2026-123633), fixed in nginx 1.30.7 / 1.31.9.

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
3
Times Used
continuous scan runs
4.4k
Continuously Checked
assets under CS
1
Vulnerabilities Found
confirmed findings
Detail

nginx is one of the most widely deployed web servers and reverse proxies on the internet, used to serve static content, terminate TLS, and front application backends. Its HTTP/2 implementation is enabled on a large share of public endpoints and, on community Kubernetes ingress-nginx, is on by default.

CVE-2026-123007, which this scanner tracks under the nickname NGINX2Shell, is an integer underflow in nginx's HTTP/2 send-window accounting. When a stream is cancelled, queued bytes are refunded to the connection send window without enforcing the HTTP/2 maximum; once the window wraps it goes negative and reaches a memory copy that writes out of bounds, which can lead to remote code execution. CVE-2026-123633 is a use-after-free that occurs when a stream is created on a connection still marked reusable after a partial HEADERS frame. Both issues were fixed by the same upstream patch, released in nginx 1.30.7 (stable) and 1.31.9 (mainline).

This scanner is a potential checker. Neither flaw can be safely confirmed with a single benign request: CVE-2026-123007 requires roughly 128 GB of HTTP/2 traffic on a single connection, and CVE-2026-123633 requires a worker_connections exhaustion race. The scan therefore reports a potential finding based on the nginx version advertised in the Server header and on whether HTTP/2 (ALPN h2) can be negotiated, which is the precondition for the critical CVE-2026-123007 path. If the version is hidden (server_tokens off), no finding is raised, to avoid false positives.

REFERENCES

Solution Advice
  • Upgrade nginx to 1.30.7 (stable) or 1.31.9 (mainline) or later. This is the only complete fix.
  • As a mitigation, disable HTTP/2: remove http2 from listen directives and set http2 off;, then reload nginx.
  • On community Kubernetes ingress-nginx, set use-http2: "false" in the controller ConfigMap.
  • Fronting nginx with a CDN or reverse proxy that terminates HTTP/2 itself (for example Cloudflare) likely breaks the CVE-2026-123007 exploitation path, because the attacker's raw HTTP/2 frames no longer reach nginx directly. Treat this as risk reduction only, not a fix; still upgrade.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.