Docker Fixes Critical Docker Hub Vulnerability That Could Allow Image Repository Impersonation

Docker has patched a critical security vulnerability in Docker Hub that could have allowed one user to push, pull, or delete container images as another user. Tracked as CVE-2026-105445, the flaw received a CVSS 4.0 score of 9.4.

The vulnerability affected Docker Hub's account conversion feature, which allows users to convert personal accounts into organizations. During this process, personal access tokens (PATs) could be transferred to the designated organization owner without their consent, while the original token secrets remained unchanged.

How the Docker Hub Vulnerability Worked

Personal access tokens allow users and automated systems to interact with Docker Hub without using account passwords. The vulnerability occurred when converting a personal account into an organization changed the recorded owner of existing tokens.

An attacker could potentially create a personal access token, convert their account into an organization, and designate another user as the organization owner. The transferred token could then operate within Docker Hub using the target user's permissions.

Depending on the token's access level, an attacker could potentially:

  • Push malicious container images to another user's repositories.
  • Pull private images accessible to the target account.
  • Delete container images within the token's permission scope.
  • Publish malicious images under a legitimate publisher's name.

The vulnerability affected Docker Hub's container registry operations. According to Docker, it did not provide access to the Docker Hub web interface or allow attackers to change account passwords, email addresses, or two-factor authentication settings.

CVE-2026-105445: A Two-Year-Old Security Flaw

The vulnerability remained present from August 26, 2024, until Docker deployed a fix on September 30, 2026. Docker disclosed the issue publicly on October 12.

The company fixed the vulnerability directly on Docker Hub, so users do not need to install a software update to address it.

Security researchers Peter Molnar and Krisztian Hozak reported the flaw, which they named GhostPat. Docker stated that it deployed the fix less than four hours after receiving their report.

Docker Reports No Evidence of Exploitation

Docker reviewed account conversions, registry logs, and token records covering the period during which the vulnerability existed. The company examined approximately 304,000 image pushes involving transferred tokens.

Docker reported that it found no evidence that the vulnerability had been exploited. It also analyzed higher-risk public images where it could not confirm that the relevant accounts belonged to the same person or team and reported finding no malware or tampering.

However, the advisory did not provide equivalent findings for all pull and deletion operations involving transferred tokens.

Docker also acknowledged that registry logs record token usage rather than the existence of unused tokens. As a result, a transferred token that was never used might not have left a record in the logs.

How Docker Addressed the Issue

Docker deployed the fix on September 30 and subsequently deactivated identified transferred tokens on October 8, except for tokens that their owners requested to retain.

The company also changed its account-conversion process to require consent before a user is designated as an organization owner. The updated process notifies the designated owner and records changes in token ownership.

Docker recommends reviewing personal access tokens and revoking any that are unfamiliar or no longer required.

Organizations using Docker Hub should take the following precautions:

  1. Review personal access tokens: Open Account Settings and select Personal Access Tokens to inspect token creation and last-used dates.
  2. Investigate unfamiliar tokens: Check tokens you do not recognize, regardless of their descriptions.
  3. Review organization membership: Look for organizations in your account switcher that you do not remember joining.
  4. Rotate automation credentials: Replace potentially affected CI/CD tokens and review their permissions.
  5. Verify published images: Check image tags, signatures, and build records for unexpected changes.
  6. Use organization access tokens: Where supported by your subscription, prefer organization-managed tokens instead of personal tokens for organization-owned automation.
  7. Review activity logs: Organization owners should inspect available registry activity logs for suspicious image pushes.

Docker said users who did not receive its notification emails were not exposed to the identified token-transfer issue and did not need to take action specifically for this vulnerability.

Key Takeaway

The Docker Hub GhostPat vulnerability demonstrates how flaws in account-management workflows can undermine container supply-chain security. By allowing personal access tokens to operate under another user's identity, the issue could have enabled unauthorized changes to container images and private repositories.

Although Docker reported no evidence of exploitation, users should review their credentials, audit image-publishing activity, and use organization-managed access tokens for automated workflows wherever possible.