Critical Docker Hub Vulnerability Allowed Attacker Impersonation and Image Tampering

Vulnerability Details

Docker has disclosed CVE-2026-105445, a critical vulnerability in Docker Hub that enabled attackers to impersonate legitimate users and manipulate container images. The flaw stemmed from improper handling of personal access tokens during the conversion of individual accounts into organizations.

The attack vector involved creating an account with a personal access token, converting that account into an organization, and designating a target user as the organization owner. Docker Hub would reassign the attacker's token to the target user without changing the secret or obtaining consent. The reassigned token then functioned with the target's permissions at the registry level, allowing attackers to pull, push or delete images in repositories accessible to the victim.

Supply Chain Implications

Docker rated the vulnerability as critical due to its potential impact on software supply chains. Attackers could publish malicious container images under legitimate user names, undermining trust in the container ecosystem. The flaw did not grant web console access or permit changes to account credentials, passwords or two-factor authentication settings, limiting the scope of compromise to registry operations only.

Remediation and Investigation

The vulnerability was introduced on August 26, 2024, and remained present until Docker received a report on September 30, 2026. The company deployed a fix to production within four hours of confirmation. Docker examined 304,000 pushes made with transferred tokens and analyzed high-risk public images, finding no evidence of exploitation. Affected users were notified on October 2, and transferred tokens were deactivated on October 8, except where owners explicitly requested retention. The platform now requires user consent before naming individuals as organization owners and no longer transfers tokens during conversion.