Docker has disclosed a critical flaw in Docker Hub, tracked as CVE-2026-105445, that let an attacker act as another user at the registry level. The attack used the “convert account to organization” feature. An attacker could create an account and a personal access token (PAT), convert the account into an organization, and name a target user as its owner. Docker Hub then reassigned the PAT to that owner without changing the token’s secret and without asking for consent, so the attacker, who already knew the secret, now held a token that authenticated as the target.
Depending on the token’s scope and the target’s permissions, that could allow pulling, pushing or deleting images in the target’s repositories and in organizations the target belongs to. Because that includes publishing images under a legitimate name, Docker rated it a software supply chain risk. It did not give web access to the account or the ability to change passwords, emails or two-factor settings. According to Docker, the behavior was introduced on August 26, 2024. Docker received a report on September 30, 2026 and had a fix in production less than four hours later. It says it found no evidence of exploitation after examining 304,000 pushes made with transferred tokens and analyzing high-risk public images. Affected users and organization owners were notified on October 2, transferred tokens were deactivated on October 8 (unless owners asked to keep them), and Docker Hub no longer transfers PATs during conversion and asks for consent before naming someone an organization owner.
How to check if you’re affected
Affected products are Docker Hub accounts that had personal access tokens during the period from August 26, 2024 to the fix. Docker says it notified impacted users and organization owners on October 2, and that users who did not receive a notification should assume they were not impacted and need no action. If you did get the notice, review your Docker Hub security settings for access tokens you do not recognize, and check recent pushes to your repositories for images you did not publish. Tokens that were transferred were already deactivated on October 8 unless the owner asked to keep them, so confirm any you kept are ones you created.