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
nginx2root-check — Read-only checker for the five nginx2root CVEs (CVE-2026-123007/123633/121810/123634/113425), fixed in nginx 1.31.9 and 1.30.7 | Kitploit
Tools/GitHubGitHub/the-devops-daily/nginx2root-check
Defensive ToolsVulnerability ScannersConfiguration AuditingInformation GatheringWeb SecurityNetwork SecurityMisconfiguration
GitHubthe-devops-daily/nginx2root-check

nginx2root-check

Read-only checker for the five nginx2root CVEs (CVE-2026-123007/123633/121810/123634/113425), fixed in nginx 1.31.9 and 1.30.7

View Repository
22 days agoNot yet reviewed
Share

nginx2root-check

A small, read-only checker for the five "nginx2root" CVEs that Xint disclosed on 18 November 2026 and that nginx fixed in 1.31.9 (mainline) and 1.30.7 (stable).

CVEBugNeeded to reach it
CVE-2026-123007Memory corruption in HTTP/2 flow controlHTTP/2 enabled
CVE-2026-123633Use-after-free in HTTP/2HTTP/2 + requests proxied to an upstream
CVE-2026-121810Use-after-free in HTTP/3HTTP/3 (QUIC) + requests proxied to an upstream
CVE-2026-123634Use-after-free in the resolverresolver + a per-request proxy_pass + mirror/SSI
CVE-2026-113425Use-after-free in the mail proxymail proxy with proxy on and auth_http

Each one is an independent, unauthenticated path to code execution as the nginx worker process. CVE-2026-123007 only needs HTTP/2, which most TLS sites turn on, so it is the one that reaches the most servers.

What it does

The script reads three things and nothing else:

  • nginx -v for the version,
  • nginx -V for the compiled-in modules,
  • nginx -T for the running configuration (read-only).

From those it prints a version verdict (vulnerable / fixed) and which of the five attack-path features are actually enabled, then maps that to a per-CVE result (each CVE gated on its own first-affected version). It never sends a request, never touches the network, and changes nothing. There is no exploit code here.

This is heuristic triage, not proof. It reads directives across the whole config dump rather than per server block, and it cannot see a distro backport. Use it to find hosts that need a closer look, then confirm by hand.

Usage

# check the local nginx (run with sudo so nginx -T can read every include)
sudo sh nginx2root-check.sh

# machine-readable
sudo sh nginx2root-check.sh --json

# check a container image instead (needs a working docker CLI)
sh nginx2root-check.sh --image nginx:1.31.8
sh nginx2root-check.sh --image myregistry/myapp:latest --json

Exit codes: 0 not affected, 1 affected, 2 fixed version but the running worker may still need a restart, 3 cannot tell.

Example

A patched image reports fixed and reminds you to restart the worker:

nginx version:    1.31.9 (branch 1.31) -> fixed
verdict:          Patched build (1.31.9 / 1.30.7 or later). Confirm the running worker was restarted.
exit code:        2

A vulnerable version with HTTP/2, a resolver and a proxied upstream lights up the matching paths:

nginx version:    1.31.8 (branch 1.31) -> vulnerable
features enabled: http2=yes http3/quic=no resolver=yes proxy_pass=yes mail_proxy=no ssl_preread=no
attack paths:
  CVE-2026-123007 HTTP/2 flow control      : YES
  CVE-2026-123633 HTTP/2 use-after-free     : YES
  CVE-2026-123634 resolver use-after-free   : likely (resolver in use; confirm per-request proxy_pass + mirror/SSI)
verdict:          Affected: a vulnerable version has at least one nginx2root feature enabled. Patch now.
exit code:        1

Sample runs against the official nginx:1.31.8, 1.31.9, 1.30.6 and 1.30.7 images, plus a deliberately vulnerable config, are in results/.

Notes and limits

  • Distro backports. Ubuntu, Debian, RHEL and others may backport the fix without changing the X.Y.Z string that nginx -v prints. When the build looks like a distro package, the script says so. Compare the full package version with your distro's advisory to be sure.
  • A reload is not enough. Installing a fixed package and reloading keeps the old worker binary running. Restart nginx or do a supported live binary upgrade so the new executable actually serves traffic.
  • nginx -T reads the config on disk. If you edited it without reloading, the running configuration may differ from what the script sees.
  • CVE-2026-123634 depends on subrequests (mirror, SSI and similar). The script flags the resolver directive as the signal; confirm the full condition by hand.

Sources

See SOURCES.md. All facts come from nginx.org, the Xint writeup, the F5 advisory and the official Docker images.

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 →