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
docker-hub-ghostpat-check — Offline Docker Hub PAT evidence checker for CVE-2026-105445. Supplied evidence only; no token collection, login or API requests. JSON/CSV/HTML reports. | Kitploit
Tools/GitHubGitHub/completetech-security/docker-hub-ghostpat-check
Defensive ToolsContainer SecurityVulnerability AnalysisConfiguration AuditingIncident Response
GitHubcompletetech-security/docker-hub-ghostpat-check

docker-hub-ghostpat-check

Offline Docker Hub PAT evidence checker for CVE-2026-105445. Supplied evidence only; no token collection, login or API requests. JSON/CSV/HTML reports.

Share
View RepositoryWebsite
124 days agoNot yet reviewed

docker-hub-pat-check by CompleteTech LLC

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

docker-hub-pat-check

Docker Hub account-conversion PAT reassignment (CVE-2026-105445)
An offline vendor-evidence recorder, not a scanner

Contents

  • Overview
  • Requirements
  • Quick start
  • Usage
  • Interpreting results
  • Reports and output
  • Safety and limitations
  • Vendor-reported facts and sources
  • Documentation
  • Contributing and security
  • License

Overview

docker-hub-pat-check is the dedicated repository for CVE-2026-105445, a historical, service-side Docker Hub exposure. Docker reports that account-to-organization conversion re-assigned personal access tokens (PATs) to the named new owner without rotating the token secret. The exposure ran from 2024-08-26 20:33 UTC until Docker's fix at about 2026-09-30 19:10 UTC.

There is no client or Docker version rule. Only Docker can say which accounts were exposed. This tool records evidence that an administrator already holds (whether Docker's notification arrived, when, and what remediation was done) and turns it into a consistent, reportable status. It never contacts Docker Hub, never tests a token, and never reads one.

[!IMPORTANT] "Not notified" is Docker's claim, not proof. Docker says accounts that received no email were not exposed. The tool records that attribution and still reports unknown. Docker also reports no evidence of exploitation; that is a vendor finding, not something this tool verifies. Registry logs show token use, not token existence, as the vendor itself notes.

Requirements

  • Python 3.10 or later on Windows, macOS or Linux.
  • Standard library only: nothing to install, no network access needed.
  • Evidence you already hold: the Docker notification (or its absence) and your own remediation record.

Quick start

python docker_hub_pat_check.py --notification received --notification-date 2026-10-02 \
  --remediation operator_revoked_or_rotated --remediation-date 2026-10-05 \
  --retained-listed-tokens no --label example-account --format json

python docker_hub_pat_check.py --inventory examples/evidence.example.json --format html --output report.html
python docker_hub_pat_check.py --evidence-csv examples/evidence.example.csv --format csv
python docker_hub_pat_check.py --help

Run the tests with python -m unittest -v.

Usage

Each record describes one account's evidence. Records can come from the command line, JSON files, CSV files, or any combination; a run is limited to 10,000 records.

InputOptionNotes
One record--label, --notification, --notification-date, --remediation, --remediation-date, --retained-listed-tokens, --evidence-sourceSupplying any of these creates one record from the command line.
JSON--inventory FILE (repeatable)One object or an array; each needs "schema_version": 1. See examples/evidence.example.json.
CSV--evidence-csv FILE (repeatable)UTF-8 with a header row. See examples/evidence.example.csv.

Record fields:

FieldValues
labelPseudonymous text, at most 512 characters (default unlabeled)
notificationreceived, not_received, unknown
notification_dateYYYY-MM-DD
remediationoperator_revoked_or_rotated, vendor_deactivated, not_done, unknown
remediation_dateYYYY-MM-DD
retained_listed_tokensyes, no, unknown (whether a token listed in the notice was knowingly kept)
evidence_sourcevendor_email, vendor_support, vendor_statement, operator_attestation

Other options:

OptionPurpose
--format csv|json|htmlReport format (default csv).
--output FILEWrite the report to a new file; without it the report goes to stdout.
--forceReplace an existing output file.
--brand NAMEOrganization name shown in the HTML report (default CompleteTech LLC).
--fail-on-findingExit 1 when any result is potentially_affected.
--version, --helpShow the tool version or full option help.

Empty or absent values count as not supplied; values are trimmed and case-insensitive. docs/REFERENCE.md documents every field, limit, output column and rule.

Exit codes

CodeMeaning
0Completed. Findings do not change this unless --fail-on-finding is set.
1--fail-on-finding was set and at least one potentially_affected result exists.
2Argument, input or output error. Takes precedence over 1.
130Interrupted. Completed observations are preserved where possible; see interruption and recovery.

Input errors versus assessment results

Structurally invalid input is an operational error (exit 2), not an assessment: unsupported fields, duplicate JSON keys, wrong types, control characters, malformed CSV or JSON, files over 4 MiB, over-long strings, unreadable files, and any value that looks like a Docker token. Error messages never echo supplied text. An unrecognized enum value or an invalid date inside an otherwise valid record is an assessment result: unknown with malformed_evidence.

Interpreting results

StatusMeaning here
potentially_affectedThe operator reports that Docker's notification was received, so the vendor considers a transferred PAT in scope, and remediation is not fully reported. Not confirmed exploitation.
fixed_version_reportedThe notification was received and the operator reports remediation with a date and no knowingly retained listed token. There is no version comparison; this means "remediation reported", never a guarantee.
unknownEvidence is missing, malformed, conflicting, out of the vendor timeline, or says only that no notification arrived. Never a clean result.

unsupported_runtime does not apply: there is no runtime lifecycle, and there is no version_status. docker_hub_pat_evidence_status gives the reason (for example vendor_unnotified_claim, conflicting_evidence, remediation_reported; the full list is in docs/REFERENCE.md), and docker_hub_pat_exploitability is always not_tested. fixed_version_reported reflects remediation the operator reports, not a verified deployed patch.

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 →