Critical Docker Hub Vulnerability (CVE-2026-105445) Exposes Container Repositories to Unauthorized Access

A critical vulnerability, identified as CVE-2026-105445, was recently disclosed in Docker Hub. This flaw permitted attackers to gain unauthorized access to other users' container repositories by exploiting a weakness in how Personal Access Tokens (PATs) were handled during the conversion of personal accounts to organizational accounts. Specifically, when a personal account was converted to an organization and an existing user was designated as the owner, the PATs associated with the original personal account were reassigned to the new organizational owner without requiring consent or rotating the token's secret. This meant an attacker could create a PAT, convert their account to an organization, name a target user as the owner, and then use the original PAT to authenticate as the target user, gaining the ability to pull, push, or delete images in the target's repositories. This vulnerability is significant because it directly impacts the integrity and security of container images, which are fundamental building blocks of modern applications. For organizations relying on Docker Hub as a central registry for their containerized workloads, the potential for unauthorized image manipulation or exfiltration is a severe concern. The fact that the vulnerability existed for over two years, from August 2024 until its fix on September 30, 2026, highlights the long-term exposure. While Docker reports no evidence of exploitation, the potential for supply chain attacks or intellectual property theft was substantial. This incident fits into a broader trend of increasing scrutiny on software supply chain security and the critical role of registries like Docker Hub. As container adoption continues to grow, the security of the artifacts stored within these registries becomes paramount. We've seen a consistent focus on securing container images, from static analysis tools to image signing and enhanced access controls. This vulnerability underscores that even seemingly minor account management workflows can introduce significant security gaps if not meticulously designed and audited. The shift towards more automated and AI-driven development workflows, as seen with Docker's recent focus on AI agents and sandboxes, further emphasizes the need for robust security at every layer, as compromised credentials or access tokens could be leveraged by automated processes. In practice, practitioners should take immediate action. First, review all existing Docker Hub Personal Access Tokens, especially those created before September 30, 2026, and revoke any that are no longer actively used or whose origins are unclear. Implement a policy of least privilege for PATs, granting only the necessary permissions and scopes. For organizations, leverage Docker Team or Docker Business subscriptions to utilize organization-specific access tokens, which offer better management and auditing capabilities. Regularly audit activity logs for unusual pushes or pulls, and ensure that any processes involving account conversions or ownership changes are subject to stringent review and multi-factor authentication. This incident serves as a stark reminder that even with trusted platforms, continuous vigilance and proactive security measures are essential.