Organisations Safe as Docker Hub Fixes CVE-2026-105445 Token Hijacking Flaw With No Exploitation

Docker Hub resolved a critical vulnerability that allowed attackers to impersonate other users by hijacking personal access tokens, according to a security advisory published on 12 October 2026. The flaw, tracked as CVE-2026-105445, had been present in the platform’s account conversion feature for more than two years. Docker deployed a fix to its production environment on 30 September 2026, less than four hours after receiving a report describing the issue.

The vulnerability stemmed from how Docker Hub handled personal access tokens when users converted personal accounts into organisations. An attacker could create an account, generate a token, and then convert that account into an organisation while naming a victim as the owner. The system would reassign the token to the victim without changing the secret or obtaining consent, allowing the attacker to authenticate as the target.

What we know

Docker rated the flaw as critical with a CVSS score of 9.4, citing the risk to software supply chains. According to BleepingComputer, the vulnerability allowed attackers to pull, push, or delete images in repositories accessible to the impersonated user. This included organisation repositories where the target had permissions. The company stated that publishing images under legitimate names posed a significant risk to downstream users who trusted those sources.

The exposure window lasted from 26 August 2024 until the fix was applied on 30 September 2026. Docker analysed 304,000 image pushes made with transferred tokens and found no evidence of exploitation, according to Cyber Security News. The company notified affected users on 2 October and deactivated transferred tokens on 8 October, except for those whose owners explicitly requested retention.

The flaw did not grant access to the Docker Hub web interface. Attackers could not change passwords, email addresses, or two-factor authentication settings, nor could they lock legitimate account holders out. The issue was limited to registry-level actions within the scope of the hijacked token. Docker confirmed that the fix was applied directly to the service, meaning no user-side updates were required.

Defender's checklist

• Review organisation ownership records to ensure no unauthorised account conversions occurred during the exposure window.
• Audit personal access tokens for any unusual activity or unexpected repository access patterns between August 2024 and September 2026.
• Verify that all transferred tokens have been deactivated, unless explicitly retained by the organisation owner for legitimate purposes.
• Monitor container image repositories for unexpected pushes or deletions that may indicate prior exploitation or ongoing issues.

The background in plain language

Personal access tokens act like digital keys that allow tools to interact with cloud services without using passwords. When a service reassigns ownership of these keys without resetting them, the original holder can still

What to do and how to stay safe

• It blocks specific attack patterns at the perimeter, not the vulnerability itself.
• Complex rules can cause false positives, blocking legitimate user traffic.
• It works best as a temporary bridge to permanent code fixes or system updates.

Virtual patching stops attacks at the edge but leaves the vulnerability intact. Use it to bridge the gap until you can apply permanent code fixes.

Step-by-step guide: Virtual Patching: Benefits, Limits and When to Use It

General security guidance from the TechWire Beat newsroom. It is not confirmed advice from the organisations named in this story.