Critical Docker Hub Flaw (CVE-2026-105445) Exposes Supply Chain to Impersonation and Image Tampering

Docker has disclosed and patched a critical security vulnerability in Docker Hub, identified as CVE-2026-105445. This flaw, which was present for over two years—from August 26, 2024, until its fix on September 30, 2026—allowed attackers to access and potentially manipulate other users' container repositories. The vulnerability stemmed from the account conversion feature, where personal accounts could be transformed into organizations. During this process, Personal Access Tokens (PATs) associated with the original account were transferred to the designated organization owner without their consent or a change in the token's secret. This meant an attacker could create an account, generate a PAT, convert the account to an organization, and name a target user as the owner. The attacker's PAT would then function as if it belonged to the target user, granting unauthorized access to their Docker Hub registry operations, including pushing, pulling, or deleting images. This vulnerability carries significant implications for any practitioner relying on Docker Hub for their container image supply chain. The ability for an attacker to impersonate another user and potentially push malicious images into trusted repositories represents a severe supply chain risk. Developers and DevOps engineers who use PATs for automated CI/CD pipelines are particularly vulnerable, as compromised tokens could have allowed attackers to inject malware into widely used base images or application components. The critical CVSS 4.0 score of 9.4 assigned to this flaw underscores its potential for widespread impact. While Docker states they found no evidence of exploitation after reviewing approximately 304,000 pushes made with transferred tokens, the mere existence of such a long-standing vulnerability in a foundational platform like Docker Hub is a stark reminder of ongoing security challenges. The broader trend in cloud-native development emphasizes the importance of supply chain security, a topic that has gained increasing prominence with incidents like the SolarWinds attack. Organizations are increasingly adopting practices like 'shift left' security, image signing, and granular access controls to protect their software artifacts. Docker's own initiatives, such as Docker Scout and Docker Hardened Images, reflect this industry-wide focus on securing the container ecosystem. This incident highlights that even with these advancements, vulnerabilities can persist in core services, necessitating continuous vigilance. The move towards OIDC connections for authentication to Docker with short-lived tokens, as recently made available for Docker Team and Business accounts, is a direct response to the need for more secure, ephemeral credentials that reduce the attack surface associated with long-lived PATs. In practice, practitioners should take immediate action. First, a comprehensive audit of all existing Docker Hub Personal Access Tokens is crucial. Any tokens that are no longer in active use or whose origins are unclear should be revoked immediately. Second, teams should prioritize migrating automated workflows from PATs to organization-managed access tokens, especially those with repository and organization management scopes, or leverage OIDC connections for CI/CD systems where short-lived, automatically rotated credentials can significantly enhance security posture. Furthermore, implementing image scanning tools and verifying image signatures should be standard practice to detect any potential tampering, even if a token is compromised. This incident serves as a critical reminder that while Docker has addressed the flaw, the responsibility for securing the software supply chain extends to how credentials are managed and utilized within development and deployment workflows.