Critical Docker Hub Vulnerability Exposed User Repositories for Over Two Years

A significant security flaw, tracked as CVE-2026-105445, was present in Docker Hub for over two years, potentially allowing one user to push, pull, or delete container images as another. The vulnerability, which Docker has now patched, was related to the process of converting a personal Docker Hub account into an organizational account. During this conversion, personal access tokens (PATs) associated with the original account were reassigned to the new organization's designated owner without revoking the original token secret or requiring consent from the new owner. This meant that an attacker could create a PAT on an account they controlled, convert that account to an organization, name a victim as the owner, and then use the original PAT to act as the victim within the Docker Hub registry. This vulnerability is critical because it directly impacts the integrity and security of the software supply chain. In a scenario where an attacker could impersonate another user, they could potentially inject malicious code into trusted container images, leading to widespread compromise for any downstream users of those images. While Docker has stated that its extensive investigation found no evidence of exploitation, the mere existence of such a long-standing flaw in a fundamental component of the container ecosystem is a serious concern. Developers, DevOps engineers, and security teams relying on Docker Hub for image distribution are directly affected, as the trust in the registry's access control mechanisms was compromised. The incident highlights a recurring theme in cloud-native security: the critical importance of robust identity and access management (IAM), especially for automated processes and API access. Personal access tokens, while convenient, represent powerful credentials. Their lifecycle management, including issuance, rotation, and revocation, must be meticulously handled. This vulnerability underscores the potential for subtle logic flaws in complex account management features to create significant security gaps. It also reinforces the industry's ongoing shift towards more granular access controls and the principle of least privilege, even within seemingly internal system operations. In practice, practitioners should immediately review all personal access tokens associated with their Docker Hub accounts, revoking any that are not actively in use or that were created during the vulnerability window (August 26, 2024, to September 30, 2026). Organizations should prioritize the use of organization-managed access tokens, which offer better oversight and control, and integrate Docker Hub activity logs into their security monitoring systems to detect any anomalous image pushes or deletions. Furthermore, this event serves as a stark reminder to implement comprehensive software supply chain security practices, including image signing, vulnerability scanning (e.g., with Docker Scout), and maintaining immutable image policies, to mitigate risks even when registry-level vulnerabilities emerge.