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
flowise-cve-2026-69254-check — Offline Flowise evidence checker for CVE-2026-69254. Flowise version and configuration evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/flowise-cve-2026-69254-check
Defensive ToolsStatic AnalysisVulnerability ScannersVulnerability AnalysisConfiguration AuditingUtilities & FrameworksSupply Chain SecurityIncident Response
Share
GitHubcompletetech-security/flowise-cve-2026-69254-check

flowise-cve-2026-69254-check

Offline Flowise evidence checker for CVE-2026-69254. Flowise version and configuration evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads.

View RepositoryWebsite
11723 days agoNot yet reviewed

flowise-cve-2026-69254-check by CompleteTech LLC

Tests Python 3.10 or newer No dependencies AGPL-3.0 or commercial license

Flowise CVE-2026-69254 Check

Offline version triage for the Flowise nodeVMOptions sandbox override (CVE-2026-69254, GHSA-3769-jgqc-cxm7; npm packages flowise and flowise-components).

flowise-cve-2026-69254-check is a single-file, standard-library Python 3.10+ checker for CVE-2026-69254. It compares reported flowise / flowise-components versions, package-lock.json entries, or a small operator-written inventory against the advisory's affected and fixed versions, and writes CSV, JSON, or an offline HTML report.

It is offline only. It reads JSON, never runs npm, never imports or executes Flowise or any package code, never contacts a target, and never submits custom-function code anywhere. The advisory is version-based, so there is no network mode.

[!IMPORTANT] A version match is evidence, not proof. potentially_affected is not confirmed exploitability, and fixed_version_reported is not a guarantee that the running process is patched. Every result carries exploitability: not_tested. A lockfile describes what an install resolves, not what a deployed process loads.

Contents

  • Requirements
  • Quick start
  • Report example
  • Inputs
  • Sanitized deployment and owner exports
  • Options
  • Interpreting results
  • Output and report identity
  • Exit codes
  • Limitations
  • Primary sources
  • Documentation
  • Development
  • License

Requirements

  • Python 3.10 or newer on Windows, macOS, or Linux. There are no third-party dependencies.
  • No Git checkout, network access, npm, or Flowise installation is needed. The checker is one file.

Quick start

python flowise_cve_2026_69254_check.py --version 3.1.2
python flowise_cve_2026_69254_check.py --version 3.1.3 --package flowise-components --format json
python flowise_cve_2026_69254_check.py --inventory package-lock.json --format html --output report.html
python flowise_cve_2026_69254_check.py --inventory inventory.example.json --fail-on-finding
python flowise_cve_2026_69254_check.py --deployment-export examples/deployment.json --format json

On systems where Python is called python3, substitute it. At least one of --version, --inventory, or --deployment-export is required. By default the report is CSV on stdout; use --format and --output to change that.

Report example

Synthetic example HTML report with five invented inputs

Synthetic example built from inventory.example.json with invented labels. View the HTML.

Inputs

Inputs are parsed as JSON only and are never executed. They are bounded (16 MiB per file, 10,000 results per run). Field-level rules, accepted lockfile versions, and rejected shapes are in docs/REFERENCE.md.

  • --version VERSION (repeatable) with --package and optional --build-source and --observe KEY=yes|no|unknown.
  • --inventory FILE (repeatable): an npm package-lock.json / npm-shrinkwrap.json (lockfile v1, v2, v3), a package.json (declaration only, always unknown), or the small checker inventory in inventory.example.json.
  • --deployment-export FILE (repeatable): a sanitized administrator export of deployments, owners and image labels; see the next section.

Sanitized deployment and owner exports

python flowise_cve_2026_69254_check.py --deployment-export examples/deployment.json --format json

This mode reads an explicit, allowlisted administrator export, not raw Docker inspect output or Kubernetes manifests. Environment, commands, registry credentials and unrelated fields are rejected. No container or application is executed or pulled.

Format. The synthetic format (examples/deployment.json) has exactly deployment_metadata_version: 1 and a deployments list.

  • Each deployment requires a bounded deployment_id, unique across every export supplied in the same run.
  • owner (128 characters) and image_digest (sha256: plus 64 lower-case hex digits) are optional, operator-supplied labels.
  • packages holds independent entries with package, version and/or version_candidates, an optional relative install_path, and package-specific observations using the existing documented keys. Precondition observations never transfer from one component to another.
  • Duplicate package/path identities within a deployment are rejected; transitive instances at distinct paths remain separate.
  • Empty or missing component metadata emits unknown coverage rows for each missing Flowise component.
  • Inputs are bounded regular JSON files (16 MiB, at most 1,000 deployments and 10,000 combined results). Existing lockfile, inventory and declaration paths remain independent.

How to read the results.

  • Neither tags nor digest strings establish package contents or a running image. Exported provenance is always deployment_metadata_unverified, and no package provenance is attested.
  • All version assessments from this mode remain unknown, including numbers inside the affected and fixed ranges. This mode cannot establish absence of findings or clear a version as fixed.
  • --fail-on-finding does not flag unknown rows, so review those rows explicitly or apply an unknown-aware downstream policy.
  • Conflicting versions remain unknown, and exact instance observations remain intact.

Output. JSON adds deployment_groups with owner, deployment and image identity and references to the original zero-based result indices. It does not collapse instances or make an aggregate safety verdict. JSON and CSV preserve deployment_id, owner, image_digest and install_path on each result; HTML displays the group labels with escaping. These labels are intentionally reportable operator metadata, so provide sanitized IDs and team names, not customer information or credentials.

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 →