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
sonicwall-sma1000-cve-2026-102255-check — Offline SonicWall SMA1000 evidence checker for CVE-2026-102255. Reported build and configuration evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/sonicwall-sma1000-cve-2026-102255-check
Defensive ToolsIndicator of Compromise (IOC) ManagementVulnerability ScannersVulnerability AnalysisScripting & AutomationConfiguration AuditingThreat Intelligence
GitHub
Share
completetech-security/sonicwall-sma1000-cve-2026-102255-check

sonicwall-sma1000-cve-2026-102255-check

Offline SonicWall SMA1000 evidence checker for CVE-2026-102255. Reported build and configuration evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads.

View RepositoryWebsite
124 days agoNot yet reviewed

sonicwall-sma1000-cve-2026-102255-check by CompleteTech LLC

SonicWall SMA1000 CVE-2026-102255 Check

Tests Checker: offline version triage Python 3.10+ Exploitability: not tested AGPL-3.0 or commercial license

SonicWall SMA1000 (6210, 7210, 8200v): Server-side request forgery
CVE-2026-102255 · offline, version-only checker

sonicwall_sma1000_cve_2026_102255_check.py is a standalone, standard-library-only Python 3.10+ tool. It triages reported SonicWall SMA 1000 (6210, 7210, 8200v) build strings against the vendor's SNWLID-2026-0017 rule table for CVE-2026-102255, a server-side request forgery (SSRF) issue.

It is offline and version-only: it makes no network requests, never contacts or probes a device, and has no network mode, because a version string cannot be answered by passive metadata. Exploitability is always not_tested.

[!IMPORTANT] Version claims are evidence, not verified runtime state. potentially_affected is not confirmed exploitability, fixed_version_reported is not a verified deployed patch, and unknown is never a clean result.

Contents

  • Scope
  • Requirements and quick start
  • Usage
  • Example report
  • Interpreting results
  • Advisory snapshot
  • Report details
  • How it works and limitations
  • Development
  • Documentation
  • Primary sources
  • Security
  • License

Scope

FieldScope
Exploit identifierCVE-2026-102255
Aliases for this same exploitNone recorded
Sources reviewed2026-10-24
Implementation stateimplemented (offline version triage)
Network modeNone

This repository is dedicated to CVE-2026-102255. Aliases and multiple affected products identify this same exploit; they do not create additional scanner scopes. Future fixes for different vulnerabilities belong in independent repositories.

Requirements and quick start

Python 3.10 or later and nothing else: no third-party dependencies and no install step. CI runs the tests on Ubuntu, Windows and macOS with Python 3.10 and 3.14.

# Triage one reported build (prints a JSON report)
python sonicwall_sma1000_cve_2026_102255_check.py --version 12.4.3-03526

# Triage the synthetic example inventory into a standalone HTML report
python sonicwall_sma1000_cve_2026_102255_check.py --inventory examples/inventory.example.json --format html --output report.html

# Show all options and exit-status meanings
python sonicwall_sma1000_cve_2026_102255_check.py --help

At least one of --version, --inventory or --csv-list is required; otherwise the run exits with status 2.

Usage

Inputs

InputFlags
Reported build(s)--version BUILD (repeatable), with optional --branch, --model (6210, 7210 or 8200v) and --workplace-interface-access true|false|unknown; these three apply only to --version values
JSON inventory--inventory FILE (repeatable): one object or an array of objects
CSV list--csv-list FILE (repeatable): header row with a version column

Inputs can be combined in one run. Builds must match <major>.<minor>.<patch>-<build> (for example 12.4.3-03526); anything else is classified unknown.

Entry fieldJSON inventoryCSV list
schema_versionRequired, exactly the integer 1Not allowed as a column
versionOptional (missing is unknown)Required column
id (or label)OptionalOptional
branch, modelOptionalOptional
workplace_interface_accessBoolean or nullOptional
custom_buildBooleanOptional
version_candidatesList of stringsOptional, semicolon separated

Input is validated strictly. Unknown fields or columns, wrong types, duplicate keys, malformed CSV, oversized values, symlinks and non-regular files are operational errors (exit 2), not assessment results. Limits: 1 MiB per input file, 10,000 entries per run, 128 characters per field and at most 50 version_candidates per entry. docs/REFERENCE.md lists the full input rules, including accepted boolean spellings and whitespace handling, and examples/inventory.example.json is a working inventory.

Output

OptionBehavior
--format json|csv|htmlReport format; json is the default
--output FILEWrite the report to FILE instead of stdout
--forceAllow --output to overwrite an existing file

--output is validated before any input is read: it may not be an input file and is not overwritten without --force. The report is written to a temporary file in the same directory and published atomically; without --force, publication cannot replace a destination that appears mid-run, and the run exits 2 where hard links are unsupported. Report text that cannot be encoded as UTF-8 also exits 2.

Exit status

CodeMeaning
0Completed; no potentially_affected result. unknown results are not a clean result.
1Completed; at least one potentially_affected result, or any unknown result with --strict.
2Operational or usage error (bad input, unreadable file, refused overwrite). Not an assessment result.
130Interrupted (Ctrl-C). See below.

--strict makes any unknown result count as a finding (exit 1), which suits automation that must not treat unclassified builds as clean.

Interruption and partial results

The report carries a complete flag (and a CSV complete column). If the run is interrupted after the output path is validated but before publication, the results completed so far are written with complete: false and the notice says the run was interrupted; the exit status is 130.

  • Interrupted before output validation finishes: nothing is written.
  • Interrupted after the report was published: the complete report is kept, a message says so, and publication is not retried.
  • Interrupted during file publication in a way that cannot be reconciled: the checker exits 130 without claiming a report was published. Check the report artifact before running again.
  • Interrupted while writing to stdout: output may be truncated and no second report is written.

docs/REFERENCE.md describes the reconciliation details.

Example report

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.

    891
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

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

    369
  • 4

    redforge

    cybersecurity91/redforge

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

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

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

    282

Explore all tools

Browse our collection of tools

View all tools →