A critical vulnerability within Docker Hub let attackers access another user’s container repositories through the use of a Personal Access Token (PAT). The flaw was potentially exploitable for over two years, but Docker says that it has found no evidence of exploitation.
The vulnerability (designated CVE-2026-105445) exploit a discrepancy with how a PAT was assigned. Docker revealed that when an account was converted into an organization, its PATs were reassigned to the named new owner, i.e. the target user. In this case, the token secret wasn’t rotated, so the attacker could still use it.
The vulnerability was detected by Peter Molnar and Krisztian Hozak, who made a responsible disclosure to Docker.
What Is Docker Hub?
Docker Hub is the largest online registry for container images, allowing users to store, share, and download them. Developers and organizations use these images when building applications.
Depending on the target’s permissions, the attacker would be able to pull, push, or delete images with the target’s repositories and connected organizations. Any tampered image would be disseminated to every system that uses it.
Docker’s Response
While classed as critical, Docker noted that the attack does not provide web access or allow an attacker to change passwords, email addresses, or two-factor settings which would potentially block legitimate account holders from accessing their account.
Docker was made aware of the vulnerability on Sept. 30, just over two years since the exposure window was open (Aug. 26, 2024). Less than four hours after being notified, Docker had released a fix for the issue. Docker also reviewed evidence of around 304,000 pushes made with transferred tokens and found no evidence of active exploitation.
Docker released a security bulletin explaining the vulnerability that it had discovered associated with PATs. Their write up explained how an attacker could create an account, then convert it into an organization and name a target user as its owner.
Advice For Security Teams
According to Docker, any user who did not receive an email explaining the situation on Oct. 2 was not exposed to any risks. For them, no action needs to be taken.
Affected users will already have had their PATs deactivated by default, unless they requested to retain them.
More broadly, security teams should review PATs (Account settings > Personal access tokens) and revoke any that they do not recognize or are out of use.
