Docker Hub Fixes Critical Flaw Enabling Account Spoofing and Unauthorized Image Pushes
GhostPat vulnerability allowed attackers to transfer personal access tokens without owner consent.
1Critical Vulnerability in Docker Hub
Docker resolved a critical vulnerability tracked as CVE-2026-105445 with a CVSS score of 9.4. Discovered by external researchers, the flaw resided within Docker Hub's account conversion workflow. It allowed unauthorized users to push, pull, or delete container images under another legitimate user's identity across the registry platform.
2Flawed Account Conversion Logic
Docker Hub does not allow direct repository transfers between accounts. Instead, users convert personal accounts into organizations while assigning an existing user as owner. The conversion mechanism automatically transferred personal access tokens to the designated owner without invalidating secrets or requiring consent from the newly named account owner.
3GhostPat Exploitation Mechanism
Dubbed GhostPat, the exploit permitted an attacker to create access tokens on a controlled account, convert it into an organization, and assign a target as owner. Because token secrets remained unchanged, attackers retained full registry access, enabling them to push malicious container images directly under the victim's verified namespace.
4Scope of Registry Access
The security boundary failure remained confined strictly to registry operations. Attackers could not access the Docker Hub web interface, alter email addresses, modify passwords, or bypass two-factor authentication settings. However, legitimate repository namespaces could be polluted, mirroring previous software supply chain attacks observed across major container registries.
5Audit and Exploitation Findings
Docker analyzed roughly 304,000 image pushes executed via transferred tokens across the two-year exposure window. The internal investigation concluded that no active malicious exploitation occurred. In most instances, conversions occurred between accounts owned by identical entities, and scanned public images showed no evidence of malware or unauthorized tampering.
6Token Invalidation and Remediation
On October 2, Docker notified affected account and organization owners regarding transferred credentials. By October 8, the registry deactivated all identified transferred tokens unless explicitly retained by their owners. Developers were instructed to rotate credentials, audit existing personal tokens, and verify digital signatures on published container images.
7Documentation and Workflow Flaws
Public documentation tracked the problematic token transfer behavior for nearly 17 months before remediation. Docker updated its docs shortly after deploying the server-side patch. The organization has since enforced explicit user consent for ownership transfers, implemented automated email notifications, and added detailed audit logging for token ownership modifications.
8Broader Supply Chain Implications
GhostPat highlights persistent identity federation risks within developer tooling and container infrastructure. Registry permissions tied to personal access tokens rather than scoped organization credentials create critical security gaps. Organizations must replace individual tokens with structured service accounts and enforce continuous image signature verification across modern deployment pipelines.