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
http2shell-check — Offline Brotli / HTTP2Shell (CVE-2026-111497) exposure and inventory checker across verified ecosystems. Python 3.10+, no dependencies or exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/http2shell-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisScripting & AutomationConfiguration AuditingInformation GatheringSupply Chain SecurityIncident Response
Share
GitHubcompletetech-security/http2shell-check

http2shell-check

Offline Brotli / HTTP2Shell (CVE-2026-111497) exposure and inventory checker across verified ecosystems. Python 3.10+, no dependencies or exploit payloads.

View RepositoryWebsite
2123 days agoNot yet reviewed

HTTP2Shell Check — Brotli decoder exposure assessment by CompleteTech LLC

Tests Python 3.10+ No dependencies AGPL-3.0 / commercial

HTTP2Shell Check

Brotli decoder exposure, with evidence.

http2shell-check assesses reported versions and component inventories for CVE-2026-111497, the Google Brotli decoder vulnerability also called HTTP2Shell or Node2Shell. These names describe the same underlying flaw. HTTP/2 is not required.

It covers native Brotli, Node.js, Bun, Python Brotli/brotlicffi, Brotli4j, Envoy, Istio, and exact Debian source-package snapshots. The standalone Python checker makes no network requests, imports no decoder, and sends no exploit payloads. Version comparisons are triage, not proof: exploitability is always not_tested, and a reported fixed version is not a verified deployed patch.

Contents

  • Requirements
  • Quick start
  • Usage
  • The report
  • Interpreting results
  • Coverage and limitations
  • Safety and privacy
  • Documentation
  • Agent skill
  • Development
  • Contributing and security
  • License and branding

Requirements

Python 3.10+ on Windows, Linux, or macOS. There is nothing to install: the checker and its tests use only the standard library. Use python3 where python is not available.

Quick start

git clone https://github.com/CompleTetech-Security/http2shell-check.git
cd http2shell-check

# Assess explicit versions
python http2shell_check.py --component brotli=1.2.0 --format json
python http2shell_check.py --component python-brotli=1.2.1 --component bun=1.4.3

# Assess an inventory and write an offline HTML report
python http2shell_check.py --inventory examples/inventory.json --format html --output report.html

# Assess the current Python environment's installed packages
python collect_python.py > runtime.json
python http2shell_check.py --inventory runtime.json --format json

Existing output files are refused unless --force is given. Keep real inventories and reports outside Git. The checker file also works when copied elsewhere; supply --logo approved-logo.png if you want a logo in HTML reports.

Usage

Supply at least one input. --component, --inventory, --pip-list, and --node-inventory are repeatable and combinable; each creates independent observations.

InputSource
--component PRODUCT=VERSIONA single version supplied on the command line.
--inventory PATHCanonical multi-component JSON inventory.
--pip-list PATHOutput of python -m pip list --format=json; only Brotli/brotlicffi entries are assessed.
--node-inventory PATHAn existing node2shell-check collector v1 file.

Common options:

OptionDefaultBehavior
--format csv|json|htmlcsvOutput format; all formats carry the same component findings and report metadata.
--output PATHstdoutAtomically publish a completed report.
--forceoffReplace an existing output file. Inputs, the checker, and logo files stay protected.
--brand NAMECompleteTech LLCHTML organization label.
--logo PATHbundled assets/logo.png for the default brand, if presentEmbed a PNG up to 1 MiB. A custom brand omits the default logo.
--fail-on-findingoffExit 1 for potentially_affected or unsupported_runtime results.
--version, --helpPrint the tool version or usage.

The canonical inventory schema, adapter details, field limits, and the complete option and exit-code reference are in docs/REFERENCE.md. Product identifiers and version rules are in the methodology. Unknown identifiers produce unknown coverage, not a guessed match.

Exit codes

CodeMeaning
0The report was written without operational errors.
1With --fail-on-finding, at least one result is potentially_affected or unsupported_runtime.
2Operational failure: invalid arguments, or an input, collection, or output error. Valid observations from other inputs are kept where possible.
130Interrupted.

An interruption during assessment publishes the completed component observations with complete=false. An interruption during output preserves an existing destination and may leave no new report. Operational errors are not assessment results, and a partial report is not a complete one.

The report

The HTML report is one offline, script-free file. It includes an embedded logo, summary counts, prioritized component observations, evidence, unknowns, coverage gaps, remediation, branch fixes, and source links. It adapts to light and dark themes and prints cleanly. Use --brand "Your Organization" --logo approved-logo.png for custom branding.

Synthetic Brotli exposure report with component counts and evidence

Open the synthetic example. The screenshots show actual generated output; no targets were scanned. See also the narrow layout and print preview.

Interpreting results

StatusMeaning
potentially_affectedThe reported version matches a verified affected interval or exact vendor package. Validate the actual deployed copy and input paths.
fixed_version_reportedThe version meets the applicable rule. Deployed patch state and safety remain unverified.
unsupported_runtimeAn older, unsupported Node.js line needs an upgrade or vendor review. This is not CVE confirmation.
unknownMissing, disputed, qualified, custom, conflicting, or uncovered evidence needs review.

Unknown results do not trigger exit code 1 but are prominently counted. A successful command is not a clean security assessment, and report counts are not an asset safety verdict. Each component copy is assessed separately, so a fixed result never erases an affected or unknown copy.

Coverage and limitations

Rules are embedded and dated 2026-10-25; they are offline snapshots, not an automatically refreshed feed. Each product identifier below is assessed by its own rule:

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.

    772
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    505
  • 3

    ARTEX

    baarai/artex

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

    420
  • 4

    redforge

    cybersecurity91/redforge

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

    345
  • 5

    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.

    260
  • 6

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    251

Explore all tools

Browse our collection of tools

View all tools →