Docker fixes a critical Docker Hub flaw that let attackers impersonate users on the registry via access tokens
A critical vulnerability in Docker Hub (CVE-2026-105445) allowed an attacker to hand one of their own access tokens to another user and act on the registry as that user. Docker has fixed it and emailed exposed users; anyone who did not receive that email needs to take no action.
What happened
Docker has published an advisory on CVE-2026-105445, an incorrect privilege assignment vulnerability in Docker Hub rated 9.4 (critical) under CVSS 4.0. The flaw lay in the feature that converts a personal account into an organization. Since August 26, 2024, the conversion reassigned the converted account's personal access tokens (PATs) to the user named as owner of the new organization, without rotating or revoking the token secret and without asking for that user's confirmation or notifying them.
According to Docker's advisory, an attacker could create an account, generate a PAT, convert the account into an organization and name a target user as its owner. The token, whose secret the attacker still held, would then authenticate to the registry as the victim. An external research team (mptrdev.com) reported the issue on September 30, 2026, and Docker deployed a fix to production that same afternoon, less than four hours later.
Scope of the risk
Within the token's scopes, the attacker could pull, push or delete images in the target user's repositories and in those of any organizations the target could access. Because that includes publishing images under a legitimate name, Docker treats this as a software supply chain risk.
The flaw did not grant access to the Docker Hub web interface, nor could it be used to change the target's password, email address or two-factor settings, or to take over the account. The exposure window ran from August 26, 2024 (20:33 UTC) to September 30, 2026. The CVE is not listed in CISA's KEV catalog of actively exploited vulnerabilities.
Who is affected
Docker Hub is a cloud service, so the fix was applied server-side and there is no patch to install. Docker reviewed every account conversion made during the exposure window and, on October 2, emailed the limited number of potentially affected users and organization owners with the subject line "Docker Hub Vulnerability Identified & Resolved". According to Docker, if you did not receive that email, neither you nor the members of the organizations you administer were exposed. On October 8, Docker also forcibly deactivated PATs transferred through conversions, with some exceptions that the available excerpt of the advisory does not detail.
What to do
Most users need to do nothing. For those who did receive the notice, or who want to confirm their status, we recommend the following steps:
- Check the mailboxes of whoever manages your Docker Hub accounts and organizations for the October 2 email with the subject line above.
- If it was received, review the access tokens on the affected accounts and revoke any you do not recognize.
- Review image push and delete activity in the affected repositories during the exposure window and verify the integrity of published images.
- Note that, after the fix, PATs are no longer transferred when converting an account: the new owner must create new ones, and Docker recommends using organization access tokens instead.
- Read Docker's advisory for full details.
Sources
Affected technologies
Vulnerabilities (1)
| CVE | Severity | Active exploitation | Published | NVD status |
|---|---|---|---|---|
| CVE-2026-105445 | Critical (9.4) | — | 10/13/2026 | Received |
Written automatically from NVD, CISA KEV and vendor advisory data. Always check affected versions and patches in the vendor's official advisory before acting.