TWO-STAGE DEMO

Separate the privileges.

Remote NGINX path→Worker privileges→Separate SCTP kernel flaw→Host root in Xint's test

Each of the five NGINX CVEs has a different configuration prerequisite. Xint demonstrated the full chain in a controlled environment, including a container escape. A vulnerable NGINX build by itself does not imply root privileges.

Xint technical analysis

PUBLIC LAB MATERIAL

One public exploit, narrow test setup.

Rapid7 published a CVE-2026-123007 repository with a trigger and a lab RCE PoC for a freshly started NGINX 1.31.8 Docker image. Rapid7 describes high traffic and environment constraints; a failed run does not prove a production server safe.

Open Rapid7's PoC repository

We do not provide an exploit command here. Use inventory and vendor advisory checks for production exposure assessment.

NON-DESTRUCTIVE CHECKS

What a version or ALPN test proves.

Check the full package version against its vendor security notice, inspect modules and effective configuration, then test whether the actual origin negotiates HTTP/2. An edge-only ALPN result cannot establish what protocol reaches NGINX.

Check HTTP/2 module and on-disk configuration
nginx -V 2>&1 | grep -- '--with-http_v2_module'
sudo nginx -T 2>&1 | grep -nE 'listen.*http2|^[[:space:]]*http2[[:space:]]+on'
Check protocol negotiation on an authorized endpoint
openssl s_client -connect HOST:443 -servername HOST -alpn h2 </dev/null 2>&1 | grep -E 'ALPN protocol:|No ALPN negotiated'
Interpret with care

These checks identify build and configuration clues. They do not prove the presence or absence of all five flaws, and a connection failure is inconclusive.