Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/weitek/nginx2root
Defensive ToolsReconnaissanceVulnerability ScannersWeb Vulnerability ScannersConfiguration AuditingInformation GatheringWeb SecurityNetwork Security
GitHubweitek/nginx2root

nginx2root

Безопасная внешняя проверка подверженности nginx уязвимостям CVE-2026-123007, -123634, -123633, -121810 и -113425. Без эксплуатации: только рукопожатие, fingerprint и разбор конфигурации.

12h 56m agoNot yet reviewed
Share
View Repository

nginx2root exposure checker

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.

Vulnerabilities

CVEWhat it isVulnerableRequired for attack
CVE-2026-123007flow control window overflow in HTTP/2 (RCE, critical)1.9.5–1.31.8HTTP/2
CVE-2026-123634use-after-free in resolver0.6.18–1.31.8resolver + proxy_pass with variable + mirror
CVE-2026-123633use-after-free in HTTP/21.19.7–1.31.8HTTP/2 + proxying to upstream
CVE-2026-121810use-after-free in HTTP/31.25.0–1.31.8HTTP/3 + proxying to upstream
CVE-2026-113425use-after-free in mail proxy0.5.33–1.31.8proxy on + auth_http

Official sources: nginx security advisories, nginx CHANGES 1.31.9, Xint analysis.

Requirements

  • Python 3.8+ (tested on 3.12), standard library only.
  • --verify requires the system CA certificate bundle.
  • Integration tests require docker and openssl.

Usage

./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:

FlagMeaning
--jsonmachine-readable report (schema below)
--port Noverride the port for all targets
--path /xpath for the fingerprint request
--timeout Sconnection/read timeout, 5 s by default
--attempts Nretries on timeout/network error (3 by default)
--no-h2-requestALPN only, no HTTP/2 request
--no-h3do not check HTTP/3 (Alt-Svc and QUIC)
--verifystrict TLS certificate verification (disabled by default)
--concurrency Nconcurrency in batch mode (2 by default)
-vdiagnostics to stderr

Exit codes: 0 — no issues found, 1 — LIKELY_VULNERABLE present, 2 — result inconclusive (CDN, unknown version, error), 3 — argument error.

What exactly is checked

  1. TLS/ALPN. A separate handshake with 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.
  2. HTTP/1.1 fingerprint. 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.
  3. HTTP/2 exchange. Preface + SETTINGS + one HEADERS (GET /). Confirms that there is indeed a live HTTP/2 behind ALPN. No control frames that affect windows.
  4. HTTP/3. The 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.
  5. Verdicts. The version is compared against ranges: 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.

How to read the output

Each CVE gets two things: a verdict (label) and an action — what to do.

LabelCodeAction
LIKELY VULNERABLELIKELY_VULNERABLEupdate nginx to 1.31.9/1.30.7
PATCHEDPATCHEDdo nothing
ATTACK PATH CLOSEDMITIGATEDdo nothing (update when possible)
NOT AFFECTEDNOT_AFFECTEDdo nothing
NOT APPLICABLENOT_APPLICABLE— (server is not nginx)
INCONCLUSIVEINCONCLUSIVEcheck manually: CDN/backport/connection error
CHECK ON SERVERUNKNOWNcheck the configuration on the host

The last line of the report is a direct answer to the question "do I need to do anything?":

VERDICTValueExit code
ACTION REQUIREDLIKELY_VULNERABLE present1
MANUAL CHECK NEEDEDINCONCLUSIVE present2
NO ACTION REQUIREDonly PATCHED/MITIGATED/NOT_AFFECTED0
CHECK NOT PERFORMEDno DNS/connection, CVEs not checked2

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 не проверялись: нет соединения с сервером.
  ИТОГ: ПРОВЕРКА НЕ ВЫПОЛНЕНА — выводов об уязвимости сделать нельзя.

Limitations

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    1.0k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    593
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    371
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    336
  • 5

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    326
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    322

Explore all tools

Browse our collection of tools

View all tools →