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
fortimail-cve-2026-104286-check — Offline FortiMail evidence checker for CVE-2026-104286. FortiMail version and deployment evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads. | Kitploit
Tools/GitHubGitHub/completetech-security/fortimail-cve-2026-104286-check
Defensive ToolsIndicator of Compromise (IOC) ManagementVulnerability ScannersVulnerability AnalysisScripting & AutomationConfiguration AuditingIncident Response
GitHub
Share
completetech-security/fortimail-cve-2026-104286-check

fortimail-cve-2026-104286-check

Offline FortiMail evidence checker for CVE-2026-104286. FortiMail version and deployment evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads.

View RepositoryWebsite
123 days agoNot yet reviewed

fortimail-cve-2026-104286-check by CompleteTech LLC

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

Fortinet FortiMail: Path traversal / NULL-byte arbitrary file write
CVE-2026-104286 · offline version assessment · exploitability never tested

fortimail-cve-2026-104286-check

fortimail-cve-2026-104286-check is the dedicated repository for CVE-2026-104286, by CompleteTech LLC. It is a standalone, standard-library-only Python 3.10+ checker that compares an operator-supplied FortiMail firmware version with the vendor's dated table of affected and fixed releases. It follows the conventions of node2shell-check and php2shell-check.

The vendor reports this flaw as exploited in the wild, so treat any potentially_affected result as a prompt to verify the appliance promptly.

  • Scope
  • Requirements
  • Quick start
  • Advisory snapshot
  • Usage
  • Interpreting results
  • Limitations
  • Primary sources
  • Development
  • Security, contributing and license

Scope

This tool is version-only and fully offline. The advisory is decided by firmware version, so there is deliberately no network mode: the tool never contacts an appliance, runs no payload, and cannot see the deployed firmware. It reads only the files you name.

  • It reports what an operator-supplied version implies against the vendor's dated table. Exploitability is always not_tested.
  • It does not scan, probe, or confirm exposure, and it is not authorization to test any system. Assess only inventories you are authorized to assess, and keep real inventories and results out of this repository.
  • Each result keeps three things separate: the version status, the precondition and mitigation observations (IBE service, webmail exposure), and exploitability.

[!IMPORTANT] A version string is evidence, not verified runtime state. Vendor backports, custom builds, and appliance configuration are not visible to this tool, and exploitability is never tested.

Requirements

  • Python 3.10 or newer (CI runs 3.10 and 3.14 on Linux, Windows, and macOS).
  • No third-party packages, installation, API key, network access, or browser.

Quick start

Run from a checkout of this repository:

# One reported version, CSV to stdout (the default format)
python fortimail_cve_2026_104286_check.py --fortimail-version 7.4.8

# The synthetic example inventory, as an HTML report
python fortimail_cve_2026_104286_check.py --inventory inventory.example.json --format html --output report.html

# Your own CSV list (see Inputs), as JSON, exiting 1 if any result is potentially_affected
python fortimail_cve_2026_104286_check.py --list appliances.csv --format json --output assessment.json --fail-on-finding

Supply the plain release number (for example 7.4.8). Build-qualified firmware strings such as v7.4.9,build0123,... are not parsed and give unknown; extract the release number yourself and confirm it on the appliance.

Advisory snapshot

Source: Fortinet PSIRT FG-IR-26-175 (updated 2026-10-07), reviewed 2026-10-24. The rule table is a dated snapshot; recheck the advisory before relying on it.

FortiMail branch8.07.67.47.27.0
Affected8.0.0-8.0.17.6.0-7.6.67.4.0-7.4.87.2.0-7.2.9sources conflict
Fixed in8.0.27.6.77.4.9none; migrate to a fixed branchnot decided
  • FortiMail 7.2 has no fix. Never infer a release is fixed beyond the table; for example 7.2.10 is unknown.
  • Fortinet says it remediated FortiMail Cloud on 2026-10-05 (firmware 7.6.7 GA or 8.0.2 GA) so Cloud customers need no action. Because this tool cannot verify a tenant, --deployment cloud stays unknown.
  • Exploitation in the wild is reported by the vendor. CISA's KEV catalog lists this CVE as an external, dated snapshot; see KEV metadata. It never changes local classification.

Mitigations are separate from version status. Vendor workarounds are to disable the IBE service, to block internet access to the FortiMail webmail interface (or restrict it to a trusted private network), or, with a web application firewall in front, to block POST requests to /ibe containing ../. Reporting them (--ibe-service disabled, --webmail-exposure restricted) lists them in the result but never changes the version status. The PSIRT page also publishes indicators of compromise; consult it rather than relying on this tool.

[!WARNING] Unresolved source conflict: FortiMail 7.0. The CVE record's structured affected data (cveawg.mitre.org) lists 7.0.0-7.0.9 as affected, but the CVE description text, the PSIRT table, and the CERT-In bulletin list only 8.0, 7.6, 7.4, and 7.2. The structured data's 7.6 and 7.4 upper bounds (7.6.5 and 7.4.6) also differ from the PSIRT table. The CVE record's CNA solution text further says "Upgrade to upcoming FortiMail version 8.0.1 / 7.6.6 / 7.4.8 / 7.2.10 or above", lists FortiRecorder fixes (7.6.1, 7.2.12, 7.0.7), and puts FortiMail Cloud at "version 25.1 (not released)"; this contradicts the PSIRT table (Solution update 2026-10-05). The PSIRT table is used, 7.2.10 is not treated as a fix, and CERT-In's "management interface" wording differs from the PSIRT's "webmail interface" (the PSIRT wording is used). Every 7.0 release stays unknown until explicit vendor evidence resolves this.

Usage

Input modes can be combined; each entry becomes its own result row (up to 10,000 per run, with input files limited to 4 MiB). Inputs must be regular files. The complete input, output, and field specification is in docs/REFERENCE.md.

Inputs

OptionDescription
--fortimail-version VERSIONAssess a reported plain MAJOR.MINOR.PATCH version (optional leading v); repeatable.
--inventory FILEJSON object or array of objects with schema_version (1) and version; repeatable. See inventory.example.json.
--list FILEUTF-8 CSV with a header row; version is required. Optional columns: label, build_source, deployment, ibe_service, webmail_exposure. Repeatable.

Example CSV list:

label,version,ibe_service
mail-a.example.test,7.6.6,disabled

--build-source, --deployment, --ibe-service, and --webmail-exposure apply to every --fortimail-version on the command line; inventory and list entries carry them per entry.

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 →