
Offline Docker Hub PAT evidence checker for CVE-2026-105445. Supplied evidence only; no token collection, login or API requests. JSON/CSV/HTML reports.
Docker Hub account-conversion PAT reassignment (CVE-2026-105445)
An offline vendor-evidence recorder, not a scanner
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.
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.
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.
| Input | Option | Notes |
|---|---|---|
| One record | --label, --notification, --notification-date, --remediation, --remediation-date, --retained-listed-tokens, --evidence-source | Supplying 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:
| Field | Values |
|---|---|
label | Pseudonymous text, at most 512 characters (default unlabeled) |
notification | received, not_received, unknown |
notification_date | YYYY-MM-DD |
remediation | operator_revoked_or_rotated, vendor_deactivated, not_done, unknown |
remediation_date | YYYY-MM-DD |
retained_listed_tokens | yes, no, unknown (whether a token listed in the notice was knowingly kept) |
evidence_source | vendor_email, vendor_support, vendor_statement, operator_attestation |
Other options:
| Option | Purpose |
|---|---|
--format csv|json|html | Report format (default csv). |
--output FILE | Write the report to a new file; without it the report goes to stdout. |
--force | Replace an existing output file. |
--brand NAME | Organization name shown in the HTML report (default CompleteTech LLC). |
--fail-on-finding | Exit 1 when any result is potentially_affected. |
--version, --help | Show 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.
| Code | Meaning |
|---|---|
0 | Completed. 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. |
2 | Argument, input or output error. Takes precedence over 1. |
130 | Interrupted. Completed observations are preserved where possible; see interruption and recovery. |
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.
| Status | Meaning here |
|---|---|
potentially_affected | The 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_reported | The 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. |
unknown | Evidence 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.