
Безопасная внешняя проверка подверженности nginx уязвимостям CVE-2026-123007, -123634, -123633, -121810 и -113425. Без эксплуатации: только рукопожатие, fingerprint и разбор конфигурации.
Safe external check: whether a site is vulnerable to the nginx2root vulnerabilities, published by Xint on November 18, 2026, and fixed in nginx 1.31.9 and 1.30.7.
The tool only performs a handshake and ordinary requests. It does not exploit
the vulnerabilities: it does not send a WINDOW_UPDATE flood, does not tear down streams via
RST_STREAM, and does not attempt to crash the worker.
| CVE | What it is | Vulnerable | Required for attack |
|---|---|---|---|
| CVE-2026-123007 | flow control window overflow in HTTP/2 (RCE, critical) | 1.9.5–1.31.8 | HTTP/2 |
| CVE-2026-123634 | use-after-free in resolver | 0.6.18–1.31.8 | resolver + proxy_pass with variable + mirror |
| CVE-2026-123633 | use-after-free in HTTP/2 | 1.19.7–1.31.8 | HTTP/2 + proxying to upstream |
| CVE-2026-121810 | use-after-free in HTTP/3 | 1.25.0–1.31.8 | HTTP/3 + proxying to upstream |
| CVE-2026-113425 | use-after-free in mail proxy | 0.5.33–1.31.8 | proxy on + auth_http |
Official sources: nginx security advisories, nginx CHANGES 1.31.9, Xint analysis.
--verify requires the system CA certificate bundle.docker and openssl../nginx2root_check.py https://example.com
./nginx2root_check.py example.com:8443 --timeout 8
./nginx2root_check.py https://example.com --json > report.json
./nginx2root_check.py --file targets.txt --concurrency 4
cat targets.txt | ./nginx2root_check.py --no-h3
Useful flags:
| Flag | Meaning |
|---|---|
--json | machine-readable report (schema below) |
--port N | override the port for all targets |
--path /x | path for the fingerprint request |
--timeout S | connection/read timeout, 5 s by default |
--attempts N | retries on timeout/network error (3 by default) |
--no-h2-request | ALPN only, no HTTP/2 request |
--no-h3 | do not check HTTP/3 (Alt-Svc and QUIC) |
--verify | strict TLS certificate verification (disabled by default) |
--concurrency N | concurrency in batch mode (2 by default) |
-v | diagnostics to stderr |
Exit codes: 0 — no issues found, 1 — LIKELY_VULNERABLE present,
2 — result inconclusive (CDN, unknown version, error), 3 — argument
error.
ALPN=["h2","http/1.1"]. If the server
negotiated h2, then HTTP/2 is enabled on this port — this is the condition
for CVE-2026-123007 and CVE-2026-123633.HEAD / and, if the version is not visible, GET to
a non-existent path: Server:, the body of the default error page, a sign of
a distribution build ((Ubuntu), (Debian)), CDN headers. OpenResty,
Tengine, Angie, Kong and APISIX are recognized as the nginx family: they
contain the nginx core and are affected by the same CVEs.SETTINGS + one HEADERS (GET /).
Confirms that there is indeed a live HTTP/2 behind ALPN. No control
frames that affect windows.Alt-Svc header with h3 and a UDP QUIC probe: an
Initial with an unsupported version is sent, and the server must respond
with Version Negotiation.1.9.5–1.31.8 and
1.30.0–1.30.6 are vulnerable; 1.31.9+ and 1.30.7+ are fixed; ≤1.9.4 are
not affected.Each CVE gets two things: a verdict (label) and an action — what to do.
| Label | Code | Action |
|---|---|---|
| LIKELY VULNERABLE | LIKELY_VULNERABLE | update nginx to 1.31.9/1.30.7 |
| PATCHED | PATCHED | do nothing |
| ATTACK PATH CLOSED | MITIGATED | do nothing (update when possible) |
| NOT AFFECTED | NOT_AFFECTED | do nothing |
| NOT APPLICABLE | NOT_APPLICABLE | — (server is not nginx) |
| INCONCLUSIVE | INCONCLUSIVE | check manually: CDN/backport/connection error |
| CHECK ON SERVER | UNKNOWN | check the configuration on the host |
The last line of the report is a direct answer to the question "do I need to do anything?":
VERDICT | Value | Exit code |
|---|---|---|
ACTION REQUIRED | LIKELY_VULNERABLE present | 1 |
MANUAL CHECK NEEDED | INCONCLUSIVE present | 2 |
NO ACTION REQUIRED | only PATCHED/MITIGATED/NOT_AFFECTED | 0 |
CHECK NOT PERFORMED | no DNS/connection, CVEs not checked | 2 |
If the check is impossible (DNS, timeout, TLS), the CVE table is not printed —
instead, the reason and a recommendation are shown. With --no-h3, the HTTP/3 verdict becomes
CHECK ON SERVER and does not affect the exit code. If UDP/443 did not respond,
HTTP/3 is also marked CHECK ON SERVER: UDP silence may mean
a filter, not the absence of HTTP/3.
Timeouts and network errors are retried up to --attempts times (default 3).
If a response is received not on the first attempt, a line appears in note:
"connection unstable: successful response received on attempt N of M".
The version is taken not only from nginx/1.30.7, but also from vendor tokens:
nginx-reuseport/1.30.7, nginx-naxsi/1.24.0, nginx-extras/1.18.0.
For such builds, a note with the original token is added.
Example:
== https://example.com ==
Проверка ВЫПОЛНЕНА
TLS TLSv1.3; ALPN=h2
HTTP/2 согласован, отвечает
HTTP/3 не обнаружен
Server nginx/1.24.0 (Ubuntu)
CDN не обнаружен
CVE-2026-123007 НЕОПРЕДЕЛЁННО дистрибутивная сборка (Ubuntu): возможен бэкпорт; HTTP/2 включён → проверить вручную
CVE-2026-123634 ПРОВЕРИТЬ НА СЕРВЕРЕ нужен resolver + proxy_pass с переменной + mirror → проверить конфигурацию на сервере
...
Сводка: НЕОПРЕДЕЛЁННО=3, ПРОВЕРИТЬ НА СЕРВЕРЕ=2
ИТОГ: НУЖНА РУЧНАЯ ПРОВЕРКА — автоматический вердикт невозможен
2 CVE проверяются только на сервере — см. docs/server-check.md
On DNS error:
== https://bad-host.invalid ==
Проверка НЕ ВЫПОЛНЕНА
Причина не удалось разрешить имя (DNS): bad-host.invalid
Что делать проверить домен/DNS и повторить проверку
CVE не проверялись: нет соединения с сервером.
ИТОГ: ПРОВЕРКА НЕ ВЫПОЛНЕНА — выводов об уязвимости сделать нельзя.