NGINX: How to Check HTTP/2 and Close Attack Vectors

NGINX: How to Check HTTP/2 and Close Attack Vectors

On November 18, five critical vulnerabilities in NGINX were disclosed; two allow remote code execution without authentication if HTTP/2 is enabled. Xint says each flaw has its own exploitation path and that the conditions depend on the configuration: disabling HTTP/2 does not cover all five.

Who should check their servers

Start with machines running NGINX to receive web or API traffic, whether they serve content directly or forward it to applications. Wiz confirmed remote code execution on a server serving static files: the backend application does not need to have a flaw for NGINX to be exposed.

CVE-2026-123007 affects official versions from 1.9.5 through 1.31.8 and requires HTTP/2 to be available and enabled. CVE-2026-123633 also requires HTTP/2, but Xint links it to requests forwarded to a backend server. The other three flaws affect different configurations:

CVEConfiguration identified by XintDoes disabling HTTP/2 mitigate it?
CVE-2026-123007HTTP/2 enabledYes
CVE-2026-123633HTTP/2 and requests forwarded to a backendYes
CVE-2026-123634resolver, request-based proxy_pass, and mirror with mirror_request_body offNo
CVE-2026-121810HTTP/3 and requests forwarded to a backendNo
CVE-2026-113425NGINX Mail Proxy with proxy and auth_httpNo

The table summarizes the conditions described by Xint; for CVE-2026-123634, the investigation warns that other functions that generate subrequests could also trigger the flaw. Removing mirror alone is not enough to consider that configuration safe.

Steps to check and respond

  1. Inventory the instances and their roles. Include NGINX installed on servers, appliances, and containers. Note whether each instance serves content, forwards requests to a backend, uses HTTP/3, or acts as a mail proxy. A shared instance may serve multiple websites and APIs, so do not limit the review to a single site.

  2. Check the installed version. Run this on the server:

    nginx -v 2>&1

    For official versions, 1.9.5 through 1.31.8 fall within the vulnerable range for CVE-2026-123007. Version 1.31.9 includes the fixes announced by Xint for its five flaws. Wiz also identifies NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline) as fixed versions for the two HTTP/2 vulnerabilities it investigated. Verify which CVEs your package covers, especially if you use a stable branch or a distribution package.

  3. Check whether the binary includes HTTP/2. For CVE-2026-123007, Xint says the module must be compiled in and HTTP/2 must be enabled. You can check the build option with:

    nginx -V 2>&1 | grep -q -- '--with-http_v2_module' \
    && echo 'HTTP2_MODULE=present' \
    || echo 'HTTP2_MODULE=absent'

    If the module is present, next check the active configuration on disk. The following command shows the lines that enable HTTP/2:

    sudo nginx -T 2>&1 \
    | sed 's/#.*//' \
    | grep -nE 'listen[[:space:]].*http2|^[[:space:]]*http2[[:space:]]+on[[:space:]]*;'

    Output may include `listen 443 ssl http2;` or `http2 on;`. Keep in mind that `nginx -T` reads the configuration files: if they have been changed but NGINX has not been reloaded, they may not match the running configuration.

  4. Check exposure from outside. If the server should be accessible from the Internet, Xint suggests checking HTTP/2 negotiation over TLS from an external machine. Replace `{HOST}` with the domain name and change the port if you do not use 443:

    openssl s_client -connect {HOST}:443 -servername {HOST} -alpn h2 </dev/null 2>&1 \
    | grep -E 'ALPN protocol:|No ALPN negotiated|Connection refused|connect:errno|handshake failure'

    `ALPN protocol: h2` indicates that HTTP/2 is accepted at the endpoint being queried. If there is a CDN or reverse proxy in front, this test reaches that service; check the NGINX server directly as well. An external result does not replace local checks of the module, configuration, and patch.

  5. Install the appropriate fix. Xint recommends NGINX 1.31.9 to fix its five vulnerabilities. If you use distribution packages, compare the full package version with its security advisory: a backported fix may not change the number returned by `nginx -v`. After installing the update, restart NGINX or complete a compatible live binary upgrade. Reloading the configuration does not replace the executable already in use.

  6. If you cannot update, temporarily disable HTTP/2. Wiz says that, in NGINX 1.25.1 or later, you can set `http2 off;` in the affected `server` blocks and remove the `http2` parameter from the `listen` directives. Test application compatibility, reload NGINX, and confirm that the old worker processes have exited. This measure blocks the CVE-2026-123007 and CVE-2026-123633 paths, but does not fix the other three vulnerabilities. Re-enable HTTP/2 after updating.

  7. Look for signs and preserve context. Xint notes that unexpected worker crashes or workers running programs may occur, but these are general indicators, not conclusive evidence of exploitation. Rapid7 describes a proof of concept for CVE-2026-123007 that requires a considerable volume of HTTP/2 traffic; the specific pattern depends on network and configuration conditions. Investigate logs and processes alongside the technical review, without interpreting an isolated crash as confirmation of an attack.

Mistakes that leave gaps

Do not treat HTTP/2 as the only risk. Disabling it reduces exposure to two CVEs, but does not address paths linked to HTTP/3, the mail proxy, or certain combinations of directives. Review those functions even if HTTP/2 is already off.

Do not decide based only on `nginx -v`. Distributions may incorporate patches without changing the main version shown by that command. Confirm the full package version and the relevant advisory; also do not assume that a recent version number means all fixes are present.

Do not confuse the external test with the actual state. A proxy or CDN may negotiate HTTP/2 even if the origin NGINX does not, or hide how the origin is configured. Verify both the front-end service and the instance running NGINX; if patch status or connectivity is unclear, the check is inconclusive.

Finally, do not leave a temporary mitigation in place as a substitute for the patch. The priority is to identify each affected instance, apply the fix that covers its vulnerabilities, and validate which configurations remain exposed.

Sources: Infosecurity Magazine, LWN.net, wiz.io, Rapid7, Xint Blog | Insights from Offensive Security Researchers