What Docker's Hub advisory says CVE-2026-105445 could do

What happened

On October 12, 2026, Docker published a Hub advisory for CVE-2026-105445. Researchers Peter Molnar and Krisztian Hozak reported the issue on September 30, 2026, through Docker's disclosure program. Docker says it deployed a fix the same afternoon, less than four hours after the report, around 19:10 UTC. The company says that beginning August 26, 2024, at 20:33 UTC, converting a personal account into an organization reassigned that account's personal access tokens to the named new owner, without rotating the secret and without asking or notifying that owner. Within a token's scope, Docker says that could pull, push, or delete images. It says the flaw did not give web-interface access or let someone change a password, an email address, or two-factor authentication. Docker says it found no evidence of exploitation. The paper filing the advisory isFutureweb.

What Docker says it did after the fix

Docker says it reviewed conversions back to the day the flaw was introduced. On October 2 it emailed users and organization owners whose accounts could have been affected. The subject line it names is Docker Hub Vulnerability Identified and Resolved. On October 8, at 3:45 PM Eastern, it deactivated the transferred tokens, except tokens whose owners had asked to keep them before the deadline. The immediate fix is that conversion no longer transfers personal access tokens. Docker also says it now requires consent before someone is named an organization owner, and that it records token-ownership changes. The desk for the advisory isSecurity.

What the other accounts add

iSec News, on October 13, reports the same identifier, the same 2024-to-2026 window, and Docker's statement that a review of about 304,000 image pushes found no evidence of malicious use. certi.news's October 12 account names the researchers and the same fix time. This page does not repeat a step-by-step account of how a conversion was abused. The form of a published advisory isthe advisory is the story.

Why it matters on this desk

The dependency is a supply-chain claim Docker itself rates as critical, limited to tokens that moved during a conversion, and closed by a server-side fix plus a later deactivation. The people in scope are those who received the October 2 email. Docker says that if you did not get the email, you were not exposed. What a CVE identifier is, as a label rather than a how-to, iswhat a CVE identifier is.

What this page will not import

The advisory includes a sequence of how a token could be aimed at another owner. This page does not reproduce that sequence, does not list commands, and does not point readers at a technical write-up in order to reconstruct it. Impact and scope are the filing. A content address, a different distributed-systems fact, iswhat a content address is.

Where the accounts overlap

Docker, iSec News, and certi.news overlap on the identifier CVE-2026-105445, the conversion window, the same-day fix, the October 2 notice, the October 8 deactivation, and the company's statement that it found no exploitation. They overlap on what the token could not do: the web account, the password, the email, and two-factor authentication. They do not overlap on a count of confirmed thefts, because the company says it found none. Consent before a person is named an organization owner is a control Docker says it added after the fix. Mark Lechner is the author on the Docker post. The researchers Docker names are Peter Molnar and Krisztian Hozak.

What to watch next

A Docker update that says exploitation was found, or that the October 8 deactivation missed a class of tokens, would change the record. Another outlet restating the advisory would not. Docker says unused tokens leave no trace, so it treated every transferred token in the window as potentially affected. That is the company's scope rule. A version number's meaning, a different software fact, iswhat a version number has to mean.

What would change the record

A correction of the August 26, 2024 start, the September 30, 2026 fix time, or the 304,000-push review would change it. A statement that web-interface takeover was possible would contradict the advisory this page is using. A write-up that adds steps is not a new impact. Mark Lechner is the author on the Docker post. The researchers Docker names are Peter Molnar and Krisztian Hozak. Organization access tokens, which Docker recommends for automation that belongs to an organization, are the company's alternative to a person's token. This page does not provide setup steps. Organization access tokens, which Docker recommends for automation that belongs to an organization, are the company's alternative to a person's token. This page does not provide setup steps.

What stays inside the token

What stays specific is a personal access token reassigned during conversion, able to do what its scope already allowed to images, and not a takeover of the Docker Hub login. The window is August 26, 2024, 20:33 UTC, through September 30, 2026, about 19:10 UTC. The people Docker says must look are the ones who got the October 2 email. About 304,000 pushes with transferred tokens stayed in the converted organization's repositories or the new owner's own repositories, and Docker says that review found no malicious use. An auditable history of token ownership changes is the other control Docker says it added. Consent before a person is named an organization owner is a control Docker says it added after the fix.