Docker Hub Vulnerability (CVE-2026-105445) Exposes Container Image Repositories

A critical vulnerability, tracked as CVE-2026-105445, was recently discovered and patched in Docker Hub. This flaw allowed an attacker to gain unauthorized access to a user's container image repositories by exploiting a weakness in how personal access tokens (PATs) were handled during the conversion of a personal account to an organization. Specifically, when a personal account was converted to an organization, the PATs associated with the original account were reassigned to the new organization's owner without revoking the token's secret or requiring consent from the designated owner. This meant an attacker could create a PAT on an account they controlled, convert that account to an organization, and name another user as the owner, effectively allowing the attacker to act as that user within the Docker Hub registry. This vulnerability is significant for practitioners because it directly impacts the integrity of the software supply chain. The ability for an unauthorized party to push, pull, or delete container images under another user's identity introduces a substantial risk of malicious code injection, tampering, or disruption of critical deployment pipelines. Even though Docker reported no evidence of exploitation, the potential for such an attack highlights the need for vigilance in managing access credentials and understanding the implications of account structure changes. Developers and DevOps teams rely heavily on Docker Hub for distributing and consuming container images, making any compromise to its security a serious concern for application reliability and trust. The incident fits into a broader, well-established trend of increasing focus on software supply chain security. As organizations increasingly adopt cloud-native architectures and leverage containerization, the attack surface expands beyond traditional application code to include build processes, registries, and runtime environments. Recent years have seen a surge in supply chain attacks, making robust authentication, authorization, and continuous monitoring paramount. Docker's introduction of features like Docker Sandboxes and AI Governance, as well as its relaunched partner program focusing on AI governance, demonstrates an ongoing effort to address these evolving security challenges within the "agentic era" of AI-driven development. In practice, practitioners should take immediate steps to mitigate similar risks. First, it is crucial to review all existing personal access tokens in Docker Hub, revoking any that are unrecognized or no longer in use. Second, for automated workflows and organizational access, prioritize the use of organization access tokens over individual PATs, as these can be managed with greater control and oversight. Organizations should also ensure that their internal security policies include regular audits of Docker Hub permissions and a clear process for handling account conversions. Furthermore, staying informed about Docker's security advisories and promptly applying any recommended actions is essential for maintaining a secure container ecosystem.