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
Tools/GitHubGitHub/foxcornlab/zip-cloaking-scanner
Defensive ToolsStatic AnalysisVulnerability ScannersVulnerability AnalysisSupply Chain Security
GitHubfoxcornlab/zip-cloaking-scanner

zip-cloaking-scanner

Detection-only triage scanner for Rust zip cloaking CVE-2026-115905: Cargo version check plus Central vs Local header comparison. No payloads, no extraction.

View Repository
21 days agoNot yet reviewed
Share

zip-cloaking-scanner

Detection-only triage scanner for Rust zip cloaking, CVE-2026-115905. It checks whether a project depends on a vulnerable zip crate, and whether a ZIP archive hides a different filename in its Local header than in its Central directory. It never exploits anything.

The flaw

DetailValue
CVECVE-2026-115905
AdvisoryGHSA-m665-v7pm-7grj (zip-rs/zip2)
BugCentral vs Local header filename mismatch (CWE-436), Zip cloaking
ImpactSecurity control bypass, arbitrary file overwrite, possible RCE
Severity10.0 / 9.9 critical, as listed in the advisory

ZipArchive reads filenames from the Central Directory File Header (CDFH) and ignores the Local File Header (LFH). ZipStreamReader does the opposite: it extracts using the LFH filename without reconciling it with the CDFH. A crafted archive can therefore pass a CDFH-first gateway inspection looking benign, then write a different attacker-selected path when a streaming extractor runs.

The advisory's own PoC test makes it concrete: CDFH says doc_report.pdf, LFH says cron_worker.sh, the gateway approves the PDF, streaming extraction overwrites cron_worker.sh.

Fixed versions

BranchStatus
zip <= 9.0.4Vulnerable
zip >= 9.0.5Fixed

Updating the zip dependency to 9.0.5 or newer is the fix. If an immediate upgrade is impossible, do not run ZipStreamReader on untrusted archives, and make gateways validate both headers before extraction.

What it checks

  • Cargo.lock for a zip package at or below 9.0.4 (vulnerable) versus 9.0.5 and above (fixed). Cargo.lock pins the exact resolved version, so it is authoritative when present.
  • Cargo.toml for a zip dependency requirement, graded on the minimum version token found. TOML requirements are ranges, so treat this as a hint and confirm with the lockfile.
  • ZIP archives, header only: it parses every Central Directory entry and reads the matching Local File Header by offset, then compares the two filenames byte for byte. A mismatch is flagged CLOAKED, a full match is CLEAN.

What it never does

No payloads. No exploitation. No extraction to disk: payload bytes are never read and extracted files are never written, so a cloaked archive cannot overwrite anything through this tool. It only reads headers and dependency files you point it at.

Grading

FindingSeverity
zip <= 9.0.4, or any CDFH/LFH filename mismatchVULNERABLE
zip >= 9.0.5 and clean headersCLEAN
No zip version found and no archive given a verdictUNKNOWN, not vulnerable
Unreadable or malformed inputERROR, not clean

Usage

# Cargo dependency check
python3 zip_cloaking.py --cargo-lock Cargo.lock
python3 zip_cloaking.py --cargo-toml Cargo.toml

# ZIP header check (headers only, nothing extracted)
python3 zip_cloaking.py --zip suspicious.zip

# Both checks, machine-readable output
python3 zip_cloaking.py --cargo-lock Cargo.lock --zip suspicious.zip --json

Exit codes: 0 = clean or unknown, 2 = vulnerable finding, 1 = scan error.

Honest caveats

  • A public PoC exists, in the advisory itself. Wild exploitation is not confirmed. This scanner does triage, not proof of exploitability.
  • A version check alone does not prove a project is exploitable: the risk needs a CDFH-first inspector feeding a ZipStreamReader extractor, or a similar decoupled pipeline. A header mismatch alone does not prove compromise either, only that the archive is cloaked and must not be trusted.
  • ZIP64 archives are supported and graded like standard archives: saturated EOCD fields are resolved via the ZIP64 record and locator, and saturated per-entry fields via the ZIP64 extra field. Malformed or truncated ZIP64 structures are still reported as errors, not clean.
  • Cargo.toml requirements are ranges. Grade the lockfile when you have it.

References

  • GHSA-m665-v7pm-7grj (zip-rs/zip2 advisory, mechanism and PoC test)
  • CVE-2026-115905 record (published 2026-10-26, affected through 9.0.4, fixed in 9.0.5)

Thanks to

  • The zip-rs maintainers for the advisory and the 9.0.5 fix
  • ByGh00st and Pr0methean, credited in the disclosure for the fix and review
  • Everyone publishing ZIP parser-differential research

Disclaimer

Built for defensive triage and authorized testing only. Scan only systems and files you own or are authorized to test. The authors are not responsible for misuse.

Research by Vineeth Kumar (foxcornlab). Found a bug or want a feature, open an issue.

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.

    1.0k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    590
  • 3

    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.

    383
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

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

    309
  • 6

    redforge

    cybersecurity91/redforge

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

    283

Explore all tools

Browse our collection of tools

View all tools →