PT-2026-111670 · Docker · Docker Hub

·

CVE-2026-105445

·

Published

2026-10-13

·

Updated

2026-10-14

CVSS v4.0

9.4

Critical

VectorAV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Name of the Vulnerable Software and Affected Versions Docker Hub (affected versions not specified)
Description An authentication bypass flaw in the management of Personal Access Tokens (PAT) allowed attackers to impersonate users and organizations. An attacker could create a personal account, generate a PAT, and convert that account into an organization while assigning a target victim as the new owner. Due to a logic error, Docker Hub transferred the ownership of the original PAT to the new owner without changing its secret or requiring the victim's consent. This enabled the attacker to use the PAT to communicate with the Registry API with the victim's privileges, allowing them to pull, push, or delete container images within the victim's repositories and any organizations they had access to. This issue posed a critical risk to the software supply chain, as malicious images could be published under trusted names. The flaw was limited to the registry level and did not grant access to the Docker Hub web interface, nor did it allow modification of passwords, emails, or two-factor authentication settings. Forensic analysis of 304,000 image pushes found no evidence of active exploitation.
Recommendations Rotate all Docker Hub Personal Access Tokens (PAT) immediately. Enable multi-factor authentication (MFA) on Docker Hub accounts. Audit repository access logs for unauthorized pulls or pushes. Use signed images with Notary or Cosign to verify image integrity.

Fix

Incorrect Privilege Assignment

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-105445

Affected Products

Docker Hub