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
simple-git-rce-check — Offline simple-git evidence checker for CVE-2026-102826. Git configuration and package evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/simple-git-rce-check
Defensive ToolsStatic AnalysisVulnerability AnalysisCode AnalysisConfiguration AuditingUtilities & FrameworksSupply Chain Security
GitHub
Share
completetech-security/simple-git-rce-check

simple-git-rce-check

Offline simple-git evidence checker for CVE-2026-102826. Git configuration and package evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads.

View RepositoryWebsite
124 days agoNot yet reviewed

simplegit-rce-check by CompleteTech LLC

Tests Python 3.10+ No runtime dependencies AGPL-3.0 or commercial license

simplegit-rce-check

Offline evidence checker for CVE-2026-102826 — simple-git configuration include command injection.

It compares simple-git version evidence that you supply (CLI values, JSON/CSV inventories, npm lockfiles, installed manifests) with the reviewed advisory rules, and can list lexical source review candidates. It never contacts websites, imports application code, runs Git or a package manager, or executes exploit payloads.

  • Scope and limits
  • Requirements
  • Quick start
  • Synthetic report preview
  • Version rules
  • Operator observations
  • Input modes
  • Options
  • Output and exit status
  • Bounds and file safety
  • Sources and references
  • Development, security and license

Scope and limits

  • Evidence triage, not a scanner. The checker covers only CVE-2026-102826 and assesses reported package-version evidence. A public URL cannot reveal an installed package inventory, and no network mode exists.
  • Reported versions are claims. Obtain each deployed package instance's exact version and provenance. Declarations, lockfiles, manifests and local workstation versions are not deployment evidence.
  • Nothing is exploited or verified in production. potentially_affected is not confirmed exploitability, and fixed_version_reported never attests an installed patch or safety. Every result retains exploitability: not_tested.
  • Uncertainty stays visible. Missing, conflicting, malformed, prerelease, qualified, vendor/custom-built and uncovered-future versions are reported as unknown. unknown is neither a finding nor a clean result.
  • Source inspection is lexical. It produces review targets only. No taint analysis, reachability test or runtime evaluation is performed.

Operate it only on evidence you are authorized to handle. Reports contain operator data; keep real targets, inventories and reports out of commits.

Requirements

  • Python 3.10 or newer, standard library only; no installation step.
  • The single file simplegit_rce_check.py can be copied and run alone. It bundles its own bounded input/reporting helpers and source lexer, and needs no companion repository at runtime.

Quick start

python simplegit_rce_check.py --version 4.0.0 --format json
python simplegit_rce_check.py --inventory examples/inventory.example.json --format html --output report.html
python simplegit_rce_check.py --csv-list inventory.csv --fail-on-finding
python simplegit_rce_check.py --help
python -m unittest -v

inventory.csv is your own file (see JSON and CSV inventories); the other inputs ship in examples/. The default output format is CSV on stdout. python -m unittest -v runs the local-only synthetic tests.

Synthetic report preview

simple-git synthetic report

Open the synthetic example report. Example data only; this is not a live assessment.

Version rules

The primary advisory and reviewed database were retrieved on 2026-10-24 (rules_as_of in every report).

Example reported versionResult
3.35.9potentially_affected
3.36.0potentially_affected
3.36.1unknown
3.99.0unknown
4.0.0fixed_version_reported
4.0.1fixed_version_reported
5.0.0unknown

Do not invent affected status for hypothetical versions between 3.36.0 and 4.0.0. include.path and includeIf variants share this advisory.

Interpreting statuses

StatusMeaning
potentially_affectedThe reported version is in the documented affected interval (up to and including 3.36.0). Application preconditions and exploitability were not established; this is not confirmed exploitability.
fixed_version_reportedThe reported version is 4.0.0 or later within the reviewed 4.x fixed line. This describes a version claim only; it never attests an installed patch or safety.
unknownAnything else: versions outside the affected interval and fixed line (no safety or other-vulnerability conclusion is made), future lines (no patch claim is extrapolated), and missing, conflicting, malformed, prerelease, qualified or custom/vendor builds.

Each row also carries a more specific version_status, such as in_documented_affected_range, at_or_above_fixed_version, outside_reviewed_range, version_not_disclosed, conflicting_versions, qualified_version_unverified, unrecognized_or_partial_version or vendor_build_unverified. The build_source value unknown (the default), upstream or official is compared as an upstream build; any other value, such as a vendor name, keeps the result unknown until independent patch evidence exists. Leading v prefixes are accepted.

Operator observations

Three optional observations describe advisory preconditions. They are supplied by the operator, unverified, and never change the package-version result.

ObservationMeaning
attacker_influence_over_clone_mirror_customargsattacker influence over clone/mirror customArgs
attacker_controlled_readable_git_configuration_fileattacker-controlled readable Git configuration file
remote_operation_loads_unsafe_configurationremote operation loads unsafe configuration

Each observation is boolean or null (not reported). Absent observations do not establish mitigation. Optional lexical source inspection is separate from them, and file-pattern findings show review targets, not proven input taint.

Input modes

At least one input is required. Modes can be combined in one run; every input produces its own rows. Unless noted, each input file must be named explicitly and is only read.

CLI versions

--version (alias --package-version) is repeatable. Each value is a separate instance, not evidence reconciliation for a single instance. --build-source and the observation flags (the observation key with underscores turned into hyphens, value true or false) apply to all CLI versions.

python simplegit_rce_check.py --version 3.36.0 --version 4.0.1 --format json
python simplegit_rce_check.py --version 4.0.0 --build-source "Example Vendor" --attacker-controlled-readable-git-configuration-file true

The second command stays unknown because the build is vendor-supplied.

JSON and CSV inventories

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.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    544
  • 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.

    385
  • 4

    redforge

    cybersecurity91/redforge

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

    360
  • 5

    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.

    302
  • 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.

    279

Explore all tools

Browse our collection of tools

View all tools →