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
cve-2026-123007-scanner — A safe, dependency-free scanner that fingerprints NGINX servers for two HTTP/2 memory-corruption vulnerabilities disclosed by F5 on 2026-11-18 | Kitploit
Tools/GitHubGitHub/materaj2/cve-2026-123007-scanner
Defensive ToolsReconnaissanceVulnerability ScannersWeb Vulnerability ScannersInformation GatheringNetwork Security
GitHubmateraj2/cve-2026-123007-scanner

cve-2026-123007-scanner

Share

A safe, dependency-free scanner that fingerprints NGINX servers for two HTTP/2 memory-corruption vulnerabilities disclosed by F5 on 2026-11-18

View Repository
11 day agoNot yet reviewed

NGINX HTTP/2 CVE Scanner

A safe, dependency-free scanner that fingerprints NGINX servers for two HTTP/2 memory-corruption vulnerabilities disclosed by F5 on 2026-11-18:

CVEClassAffected NGINX OSSImpact
CVE-2026-123007HTTP/2 flow-control integer underflow → heap buffer overflow (CWE-191 → CWE-787)1.9.5 – 1.31.0Worker crash (DoS); RCE where ASLR is off/bypassed
CVE-2026-123633HTTP/2 use-after-free under low worker_connections in a reverse-proxy config (CWE-416)1.19.7 – 1.31.0Worker crash (DoS); RCE where ASLR is off/bypassed

The scanner is non-destructive. It never attempts to trigger the bug (that could crash the target, and the real trigger is undisclosed). Instead it checks the two network-observable preconditions: whether HTTP/2 is actually served, and whether the reported NGINX version is in the affected range.

Features

  • Detects both CVEs in one pass.
  • HTTP/2 detection via TLS ALPN (h2) or cleartext h2c (prior-knowledge preface).
  • Version fingerprint from the Server header, matched against each CVE's range.
  • Bulk scanning: multiple targets, a targets file, stdin, or CIDR expansion.
  • Concurrency with a configurable worker pool.
  • Output as human-readable text, JSON, or CSV.
  • Meaningful exit codes for automation.
  • Pure Python 3 standard library — no dependencies.

Requirements

  • Python 3.6+
  • No third-party packages.

Install

git clone https://github.com/<your-org>/nginx-http2-cve-scanner.git
cd nginx-http2-cve-scanner
python3 scanner.py --help

Or just download scanner.py and run it directly.

Usage

python3 scanner.py [targets ...] [options]

Targets:
  host[:port]          cleartext h2c (default port 80)
  https://host         TLS (ALPN h2), default port 443
  host:port            with --tls for TLS on a custom port
  10.0.0.0/24[:port]   a CIDR is expanded to one scan per host address

Options:
  -f, --input FILE     read targets from FILE (one per line, '#' comments);
                       '-' means stdin; may be given multiple times
  --stdin              also read targets from stdin
  --tls                force TLS (ALPN h2) for bare host[:port] targets
  --timeout SECONDS    per-connection timeout (default 5.0)
  -w, --workers N      concurrent scans (default 20)
  --json               emit JSON
  --csv FILE           write CSV to FILE ('-' = stdout)
  --only-affected      print only affected targets

Examples

# single target (cleartext HTTP/2)
python3 scanner.py scanme.example.com

# TLS target
python3 scanner.py https://scanme.example.com
python3 scanner.py --tls scanme.example.com:8443

# bulk from a file, 50 workers, only show hits
python3 scanner.py -f targets.txt -w 50 --only-affected

# scan a whole subnet
python3 scanner.py 10.0.0.0/24 -w 100

# read targets from a pipe
cat hosts.txt | python3 scanner.py -f -

# machine-readable output
python3 scanner.py -f targets.txt --csv results.csv
python3 scanner.py -f targets.txt --json > results.json

Output

========================================================================
10.0.0.5:80  (h2c)
  Server : nginx/1.27.4
  HTTP/2 : yes
  [!] CVE-2026-123007  likely-affected
      nginx 1.27.4 is in the affected range 1.9.5..1.31.0; needs HTTP/2 enabled (present here)
  [!] CVE-2026-123633  likely-affected
      nginx 1.27.4 is in the affected range 1.19.7..1.31.0; also needs reverse-proxy config + worker low on worker_connections (verify locally)
========================================================================
[*] summary: 1 scanned, 1 affected, 0 error(s)

Verdicts

VerdictMeaning
likely-affectedHTTP/2 is served and the version is in the affected range
potentially-affectedHTTP/2 is served but the version is hidden (server_tokens off); verify the build manually
not-affectedVersion is outside the affected range
not-exposedHTTP/2 is not served on this endpoint

Exit codes

CodeMeaning
2At least one target is likely-affected or potentially-affected
1No target was affected, but at least one scan errored
0All targets scanned clean

How detection works

  1. HTTP/2 reachability. For TLS, the scanner performs a handshake offering ALPN h2 and checks whether the server selects it. For cleartext, it sends the HTTP/2 connection preface plus an empty SETTINGS frame and checks whether the server replies with its own SETTINGS frame.
  2. Version fingerprint. A single plain GET / reads the Server header and parses the nginx/X.Y.Z version.
  3. Range match. The version is compared against each CVE's affected range.

Because CVE-2026-123633 additionally requires a reverse-proxy configuration and a worker that is low on worker_connections, neither of which is visible over the network, a positive there is reported with a "verify locally" note.

Limitations

  • Version-based detection trusts the Server header; a hidden or spoofed banner weakens confidence (reported as potentially-affected).
  • The exact fixed build is defined by F5's advisories; confirm the patched version for your distribution. The scanner treats versions above 1.31.0 as out of range.
  • This tool does not confirm exploitability; it reports exposure.

Mitigation

  • Upgrade NGINX to the fixed build (F5 K000163926 for CVE-2026-123007, K000163928 for CVE-2026-123633).
  • Interim: disable HTTP/2 (http2 off;) on exposed servers. For CVE-2026-123633, also size worker_connections with real headroom so the worker is not starved.

Authorized use only

Scan only systems you own or are explicitly authorized to test. The scanner is non-destructive, but unauthorized scanning may still be unlawful in your jurisdiction. You are responsible for how you use it.

References

  • CVE-2026-123007: https://www.cve.org/CVERecord?id=CVE-2026-123007 · F5 K000163926
  • CVE-2026-123633: https://www.cve.org/CVERecord?id=CVE-2026-123633 · F5 K000163928

Credits

Developed for the SECPlayground Platform — https://www.secplayground.com

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 →