Docker Hub Vulnerability: Personal Access Tokens Exposed During Account Conversion

Docker recently disclosed a critical vulnerability, tracked as CVE-2026-105445, in Docker Hub's identity and access management system. The flaw specifically affected the process of converting a personal Docker Hub account into an organization. During this conversion, personal access tokens (PATs) associated with the original personal account could be inadvertently reassigned to the user designated as the organization's new owner. This meant that a PAT, which acts as a substitute for a password for registry operations, could be used by an unintended party to push, pull, or delete images within the target's repositories or any organizations the target had access to. This vulnerability is significant for practitioners because it directly impacts the security of their container image supply chain. The ability for a transferred PAT to publish images under a legitimate name poses a substantial software supply chain risk. While Docker has stated they found no evidence of exploitation, the potential for unauthorized access to image repositories is a serious concern, especially given the increasing reliance on containerized applications and automated CI/CD pipelines. Developers and DevOps teams who use Docker Hub for storing and distributing their images are directly affected, as compromised PATs could lead to the injection of malicious images or tampering with existing ones. The incident highlights a broader, well-established trend in cloud-native security: the critical importance of robust identity and access management, particularly for programmatic access. As organizations increasingly adopt microservices and automated deployments, the attack surface expands, making credentials like PATs prime targets. This vulnerability is a stark reminder that even seemingly minor configuration or process flaws can have far-reaching security implications. The shift towards agentic workflows and AI agents, which often interact with container registries programmatically, further amplifies the need for granular access controls and regular security audits. In practice, all Docker Hub users should immediately review their personal access tokens in their account settings and revoke any that are unrecognized or no longer in use. For automation that belongs to an organization, the recommendation is to use organization access tokens instead of individual PATs, as these offer better management and auditing capabilities. Organizations with Docker Team or Docker Business subscriptions can leverage activity logs to review past pushes and identify the tokens used, providing an additional layer of oversight. Furthermore, this event should prompt a broader re-evaluation of credential management strategies, emphasizing the principle of least privilege and the regular rotation of access tokens.