NGINX2Shell Checker.
A flaw in nginx's HTTP/2 code (CVE-2026-123007) can crash workers or run code. Check a site or paste your version.
Passive check on sites you own: one GET of your homepage to read the Server header, and one TLS handshake to see whether HTTP/2 is offered. No HTTP/2 frame, no exploit.
Test Your Server For CVE-2026-123007.
NGINX2Shell is our name for CVE-2026-123007, a heap out-of-bounds write in nginx's HTTP/2 flow control. It affects nginx 1.9.5 to 1.31.8 when HTTP/2 is on and is fixed in 1.31.9 and 1.30.7. This free checker reads the version a site advertises and whether it offers HTTP/2, or checks a version you paste, and tells you what to do on the server.
Why NGINX2Shell Matters.
nginx Sits In Front Of Everything
nginx terminates TLS and proxies traffic for a large share of the web, often in front of every other app you run. A memory-corruption flaw in its HTTP/2 code is reachable by anyone who can open a connection to it.
A Public Proof Of Concept Exists
nginx fixed CVE-2026-123007 in 1.31.9 and 1.30.7 on 18 November 2026, and Rapid7 has published a proof of concept. F5 rates it CVSS 4.0 9.2. The time between a public exploit and real attacks is short.
Hidden Does Not Mean Patched
Most sites hide the nginx version and many sit behind a CDN. That hides the number from scanners, not the flaw from attackers. Read the real version with nginx -V on the server.
Old Branches And Distributions Lag
Branches older than 1.30 get no fix, and distribution packages keep their old numbers when they backport one. On 18 November 2026 Debian had not shipped a fixed package yet.
How The Check Works.
- 01
Enter A Site Or Paste A Version
Type the domain, IP or URL of a site you own, or paste the output of nginx -V, a Docker tag or a package version.
- 02
Run The Check
For a site we make one GET of the homepage and read the Server header, then one TLS handshake to see whether HTTP/2 is offered. No HTTP/2 frame and no exploit is sent. A pasted version is compared with the advisory without contacting your server.
- 03
Read The Verdict
See the version we read and where from, the CDN in front, the HTTP/2 answer, the fixed release and the commands to confirm on the server. If something is hidden, we say so plainly.
What The Check Cannot See.
A hidden version, other server blocks, names and ports, and the origin behind a CDN. The HTTP/2 answer belongs to whatever ends the TLS connection, which may be a CDN or load balancer rather than your nginx. Distribution packages may carry a fix their number does not show. The check never confirms that the flaw can be exploited.
The Facts. With Sources.
| Fact | What Is Known | Source |
|---|---|---|
| Flaw | Memory corruption in HTTP/2 flow control (ngx_http_v2_module): a cancelled stream can push the window past 2^31-1, a later WINDOW_UPDATE check underflows into a heap out-of-bounds write. | |
| Impact | Worker crash; code execution possible when ASLR is off or bypassed. | |
| Severity | CVSS 3.1 8.1 (High), CVSS 4.0 9.2 (Critical), both scored by F5. | |
| Affected | nginx open source 1.9.5 to 1.31.8, only with HTTP/2 enabled (http2 on; or listen ... http2; off by default). | |
| Fixed | 1.31.9 (mainline) and 1.30.7 (stable). Branches 1.9.5 to 1.29 get no fix. Upgrade, then restart; a reload keeps the old binary. | |
| NGINX Plus | 37.0.0 to 37.0.7.1 fixed in 37.0.8.1; 37.1.0 to 37.2.0.1 fixed in 37.3.0.1. Older R-series releases: sources disagree, check with F5. | |
| Workaround | F5 lists none. Researchers recommend turning HTTP/2 off (http2 off; or removing http2 from listen) until you can upgrade. | |
| Exploitation | Public proof of concept by Rapid7. Not in CISA KEV; no confirmed exploitation in the wild. | |
| Debian | bookworm (1.22.1), trixie (1.26.3), forky and sid (1.30.6) listed as vulnerable, no fixed package yet. |
FAQ
Common Questions.
NGINX2Shell is Brandefense's name for CVE-2026-123007, a memory-corruption flaw in nginx's HTTP/2 module. Cancelling a stream can push the HTTP/2 flow-control window past its limit, and a later check underflows into a heap out-of-bounds write. That crashes the worker, and F5 says code can run when ASLR is off or bypassed. F5 rates it CVSS 3.1 8.1 (High) and CVSS 4.0 9.2 (Critical).
nginx open source 1.9.5 to 1.31.8, when HTTP/2 is enabled. The fixes are nginx 1.31.9 (mainline) and 1.30.7 (stable), released on 18 November 2026. Older branches from 1.9.5 to 1.29 get no fix, so move to 1.30.7 or 1.31.9. Releases before 1.9.5 have no HTTP/2 module and are not affected by this flaw, though they are long out of support.
No. The flaw is in the HTTP/2 code, which only runs when a server block has http2 on; or a listen line with http2. HTTP/2 is off by default in nginx. Many setups turn it on for TLS sites, so check every server block with grep -R "http2" /etc/nginx, and upgrade anyway: a later config change can turn it back on.
For a site, it makes one ordinary GET request to your public homepage (HTTPS first, HTTP if that fails) and reads the nginx version in the Server header, plus signs of nginx such as its own error page. Then it makes one TLS handshake on port 443 and reads whether the server offers HTTP/2 (ALPN). It sends no HTTP/2 frame and no exploit or trigger request. For a pasted version, nothing is sent to your server at all: the text is compared with the advisory. Only check sites you are authorised to test.
No. Most nginx sites hide the version with server_tokens off, and a hidden version is not a patched one. Run nginx -V on the server (or paste its output here) and compare it with 1.31.9 and 1.30.7. A CDN or proxy in front of the site also hides what runs behind it; the check names it when it can.
No. Distributions fix security bugs without changing the upstream number, so a package such as 1.22.1-9+deb12u10 or 1.24.0-2ubuntu7.1 can carry a fix the number does not show. The check calls such builds Distribution Build, Fix Unconfirmed and points you to your vendor's tracker. On 18 November 2026 Debian listed every release as still vulnerable.
NGINX Plus has its own releases: F5 lists fixes in 37.0.8.1 and 37.3.0.1, and sources disagree on older R-series releases, so check F5 article K000163926. Its Server header shows only the open-source base version. OpenResty, Tengine, Angie and freenginx ship their own release numbers on top of the nginx code, so the check names them and asks you to confirm with their vendor.
Rapid7 has published a proof of concept. At the time of writing (18 November 2026) the flaw is not in CISA's Known Exploited Vulnerabilities catalog and there is no confirmed exploitation in the wild. A public proof of concept shortens the time to attacks, so plan the upgrade now.
Upgrade to nginx 1.31.9 or 1.30.7 (or your distribution's fixed package) and restart nginx; a reload keeps the old binary running. F5 lists no workaround. Until you can upgrade, researchers recommend turning HTTP/2 off: remove http2 from every listen line and set http2 off;, then reload.
Xint, the research team credited with this flaw, groups it with other nginx flaws from the same review under the name NGINX2Root. The nginx 1.31.9 and 1.30.7 releases fix several of them at once. This checker covers CVE-2026-123007 only; the upgrade covers them all.
Related checks: HTTP2Shell checker and PHP2Shell checker.
One Server Checked. See Your Whole Edge.
This tool reads one site or one version. Brandefense External Attack Surface Management finds every internet-facing nginx you run, checks each one and flags new CVEs as they land.
Request A Demo