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
tinypool-options-rce-check — Offline Tinypool evidence checker for CVE-2026-104849. Worker-pool package and options evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/tinypool-options-rce-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisConfiguration AuditingSupply Chain Security
GitHubcompletetech-security/tinypool-options-rce-check

tinypool-options-rce-check

Offline Tinypool evidence checker for CVE-2026-104849. Worker-pool package and options evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads.

Share
View RepositoryWebsite
124 days agoNot yet reviewed

tinypool-options-rce-check by CompleteTech LLC

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

tinypool-options-rce-check

Offline evidence checker for CVE-2026-104849 — Tinypool worker-options prototype-pollution gadget (alias GHSA-85c8-ppgw-ccpr).

It compares operator-reported tinypool versions with the reviewed advisory rules and writes CSV, JSON or HTML reports. It is version-evidence triage only: it never contacts websites, imports application code, runs a package manager, or executes exploit payloads, and exploitability is always reported as not_tested.

Contents

  • Scope
  • Requirements
  • Quick start
  • Synthetic report preview
  • Reviewed rules
  • Interpreting results
  • Preconditions
  • Providing evidence
  • Options
  • Reports and output
  • Exit status and interruption
  • Limitations
  • Sources and provenance
  • Project documents
  • Contributing and security
  • License and brand assets

Scope

This repository covers only CVE-2026-104849. The checker does not scan deployed systems, fetch package inventories, analyze source code, or test exploitability. It reads versions and optional observations that you supply and reports what those claims imply under the reviewed rules.

A public URL cannot provide installed package inventory. Obtain each deployed package instance's exact version and provenance; declarations and local workstation versions are not deployment evidence. Use it only with inventories you are authorized to assess.

Requirements

  • Python 3.10 or newer, standard library only. No runtime dependencies and no network access.
  • tinypool_options_rce_check.py can be copied and run on its own; no companion repository is needed at runtime.
  • The CI workflow (.github/workflows/tests.yml) runs the local-only tests and --help on Python 3.10 and 3.14 on Ubuntu and Windows.

Quick start

# Assess one reported version; the default format is csv
python tinypool_options_rce_check.py --version 2.1.2 --format json

# Assess a JSON inventory and save an HTML report to a new file
python tinypool_options_rce_check.py --inventory examples/inventory.example.json --format html --output report.html

# Assess a CSV list and exit 1 if any entry is potentially affected
python tinypool_options_rce_check.py --csv-list inventory.csv --fail-on-finding

# Show all options, then run the local tests
python tinypool_options_rce_check.py --help
python -m unittest -v

examples/inventory.example.json is a synthetic entry (2.1.2, label example-package-instance, all observations null). Without --output, the report goes to stdout.

Synthetic report preview

Tinypool synthetic report

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

Reviewed rules

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

Example reported versionResult
2.0.9potentially_affected
2.1.0potentially_affected
2.1.1unknown
2.1.2fixed_version_reported
2.1.3fixed_version_reported
2.2.0unknown
3.0.0unknown
  • Affected interval: 0.0.0 through 2.1.0 inclusive.
  • Fixed line: 2.1.x, fixed in 2.1.2. Future lines remain unknown rather than extrapolating a patch claim.
  • Disputed boundary: 2.1.1. The maintainer range (<=2.1.0) and the GitHub Reviewed range (<2.1.2) disagree there, so it is reported as unknown and never as clean. Obtain maintainer evidence.
  • Not the trigger: pool.run(task) alone is not the documented trigger.
  • Severity: the maintainer rates it High; the database rates it Critical. Retain provenance when reporting.

Only plain stable MAJOR.MINOR.PATCH versions are compared. A single leading v and surrounding ASCII whitespace are accepted.

Interpreting results

StatusMeaning
potentially_affectedThe reported version is in the documented affected interval. This is not confirmed exploitability: preconditions and exploitability were not established.
fixed_version_reportedThe reported version is at or above the fix within the reviewed 2.1.x line. This describes a version claim only; it never attests an installed patch or safety.
unknownEvidence is insufficient to classify. This is neither a clean result nor a finding.

Every result retains exploitability: not_tested. evidence_type is operator_reported_version; evidence_confidence is insufficient for unknown and low otherwise.

Each result also carries a more specific version_status:

version_statusStatusCause
in_documented_affected_rangepotentially_affectedVersion is within 0.0.0–2.1.0.
at_or_above_fixed_versionfixed_version_reportedVersion is 2.1.2 or later within 2.1.x.
source_discrepancyunknownVersion is 2.1.1, where the sources disagree.
outside_reviewed_rangeunknownVersion is outside the affected interval and the reviewed fixed line; no safety or other-vulnerability conclusion is made.
vendor_build_unverifiedunknownbuild_source is a custom or vendor build, which needs independent patch evidence.
qualified_version_unverifiedunknownPrerelease, nightly/rc or suffixed versions need vendor verification.
unrecognized_or_partial_versionunknownVersion text is malformed or partial.
version_not_disclosedunknownNo version was reported. Missing metadata does not establish that the runtime is unaffected.

Operational failures (bad arguments, unreadable or invalid input, output errors) are not assessment results. They exit with status 2 and are never reported as unknown or clean.

Preconditions

The advisory describes conditions that must hold for the gadget to matter. You can record your own observations of them:

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 →