External risk intelligence

Docker Hub PAT Reassignment Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-105445

The vulnerability exists within Docker Hub, which is a public-facing, cloud-based container registry service. As a globally accessible SaaS platform designed for public and private image hosting, its authentication and account management features are exposed to the internet by design for all users.

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability affects Docker Hub's account management, allowing an authenticated user to gain unauthorized access to another user's repositories by reassigning their own access token. This could lead to the unauthorized retrieval, modification, or deletion of sensitive container images.

  • Token reassignment grants unauthorized registry access.
  • Protects intellectual property in container images.
  • Confirm exposure and assess impact on image repositories.

Attack Path

How an attacker could exploit the issue

An attacker with a personal access token could leverage Docker Hub's account-to-organization conversion feature to reassign their existing token to another user. This allows the attacker to impersonate the other user, gaining the same access to Docker Hub's registry for image manipulation operations.

  • Authenticated user with a PAT.
  • Account-to-organization conversion feature.
  • Unauthorized registry access.

Live Threat

Current exploitation, exposure, and threat context

An authenticated attacker could reassign a personal access token (PAT) to another Docker Hub user. The unchanged PAT could then authenticate as the recipient, allowing the attacker to perform actions such as pulling, pushing, or deleting images within that user's accessible repositories.

  • Stored Docker Hub images and access controls.
  • Attacker reassigns a controlled PAT to a target user.
  • Unauthorized image access, modification, or deletion.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in Docker Hub's account conversion feature allows an authenticated attacker to hijack personal access tokens (PATs) to impersonate other users. The first practical step is to identify all PATs currently in use, confirm their associated accounts, and assess any potentially compromised repositories. Technical leaders and security teams should coordinate with vendor management and platform teams to address this issue, prioritizing actions based on the exposure and impact of affected accounts and repositories.

  • Account owners should audit PATs for unauthorized reassignment.
  • Verify all existing PATs and their scopes.
  • Plan for PAT rotation and enhanced monitoring.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Docker Hub and how is it used?

Docker Hub is a cloud-based registry service that functions as a central repository for container images. Developers and organizations use it to store, manage, and share images, which are essentially packages containing the software and dependencies needed to run applications across various computing environments.

What is the vulnerability class for CVE-2026-105445?

This vulnerability is classified as Incorrect Privilege Assignment (CWE-266). In the context of CVE-2026-105445, it means the platform failed to properly manage the relationship between a Personal Access Token and its owner, allowing the token's permissions to be wrongly transferred to another user's account.

How can an attacker trigger this CVE-2026-105445 vulnerability?

An attacker needs an existing Personal Access Token and must interact with the account-to-organization conversion feature. The bug is not triggered by public access alone; it specifically requires the attacker to be authenticated and to misuse this specific conversion process to reassign their token to a target user.

Is my organization at risk from CVE-2026-105445?

Halo Surface Signal notes that because Docker Hub is a public-facing, cloud-based registry designed for global access, its authentication mechanisms are inherently exposed to the internet. If your team manages container images on this platform, you should consider the potential for unauthorized access to your repositories through these account-level manipulations.

How should I respond to this Docker Hub vulnerability?

Start by auditing all active Personal Access Tokens and verifying the accounts they are linked to. Check your repository logs for any unexpected activity or unauthorized changes. Prioritize rotating any tokens that appear suspicious and coordinate with your team to enhance monitoring of account-to-organization transitions.

References