Docker Hub Vulnerability Exposes Software Supply Chain to Impersonation Attacks

Docker has disclosed and patched a critical vulnerability in Docker Hub, identified as CVE-2026-105445. The flaw allowed unauthorized users to impersonate legitimate users and publish container images under their names. This vulnerability originated from a misconfiguration in how personal access tokens (PATs) were reassigned during the conversion of a personal Docker Hub account into an organizational account. Specifically, when an account was converted, its PATs were transferred to the new organization's owner without revoking the original token secret or notifying the new owner. This created a window for potential abuse, as an attacker could create an account, generate a PAT, then convert the account to an organization, naming a target user as the owner, effectively gaining control over the target's repositories via the transferred PAT. This vulnerability is significant for any organization relying on Docker Hub for their container image distribution and consumption. The ability for an attacker to push malicious or compromised images under a trusted publisher's name poses a direct threat to the software supply chain. Developers pulling these images could inadvertently integrate backdoors, malware, or other vulnerabilities into their applications, leading to widespread compromise. The impact extends beyond individual developers to entire CI/CD pipelines and production environments that automate image pulls from Docker Hub. It underscores the critical importance of verifying image provenance and implementing robust supply chain security measures. This incident fits into a broader trend of increasing attacks targeting software supply chains. As organizations increasingly adopt containerization and microservices architectures, public registries like Docker Hub become attractive targets for adversaries. Recent years have seen a rise in incidents involving compromised packages, malicious code injection, and credential theft aimed at disrupting or subverting the software delivery process. This vulnerability highlights the ongoing challenge of securing complex ecosystems where trust relationships are implicitly established through shared platforms and public repositories. The industry is continuously evolving its defenses, with initiatives like SBOMs (Software Bill of Materials), enhanced image signing, and stricter access controls becoming more prevalent to mitigate these risks. Practitioners should immediately review their Docker Hub personal access tokens, revoking any that are old, unused, or have overly broad permissions. Organizations should enforce the principle of least privilege for all credentials and consider implementing token rotation policies. Furthermore, it's crucial to implement image scanning in CI/CD pipelines to detect known vulnerabilities and malware in container images, even those from trusted sources. While Docker has patched the vulnerability and notified affected users, the incident serves as a stark reminder that continuous vigilance and a multi-layered security approach are essential for maintaining the integrity of containerized applications throughout their lifecycle. Developers should also be aware of Docker's recent changes requiring consent for organization ownership transfers and notifications for such events.