Docker Hub IAM Vulnerability and Remediation

What Changed Operationally

Security researchers identified a vulnerability in Docker Hub’s identity and access management system on September 30, 2026, which was subsequently tracked as CVE-2026-105445. The flaw allowed personal access tokens (PATs) to be transferred to a new owner during account-to-organization conversions without the recipient's consent. This exposure window ran from August 26, 2024, until a fix was deployed on September 30, 2026, creating a potential gap where credentials could be misappropriated during administrative transitions. The operational impact of this issue is significant because it bypassed the standard consent mechanisms required for credential ownership, potentially allowing a new organization owner to inherit the authentication rights of a previous user. Docker confirmed the report and deployed a production fix within four hours, but the retrospective analysis required a comprehensive review of account conversion logs and authentication records to determine the scope of the exposure.

To address the operational risks associated with this incident, Docker Hub has implemented a series of administrative and technical changes designed to prevent the unauthorized transfer of credentials and provide greater visibility into ownership changes. The company reviewed every account conversion back to the date the flaw was introduced and notified every user and organization owner whose account could have been impacted by this vulnerability on October 2. Following this notification, Docker deactivated the identified transferred PATs on October 8, excluding any tokens whose owners explicitly requested they be retained. To mitigate future occurrences, the platform now requires explicit consent from a user before they are named as an organization owner and notifies them immediately when this occurs. Furthermore, Docker is recording an auditable history of every token ownership change and is actively reviewing other flows that change credential ownership for the same pattern. This shift ensures that administrative actions are no longer opaque and that users retain control over their authentication credentials.

Architecture of the Vulnerability and Fix

How The Capability Fits Together

The underlying mechanism of this vulnerability resided in the IAM token handling logic during the account-to-organization conversion process. The flaw allowed PATs associated with a personal account to be transferred to the new organization owner as part of the migration workflow. This behavior created a scenario where the new owner possessed the authentication credentials of the previous account, effectively merging the access rights without the standard consent gate. The exposure window was defined by the period between the introduction of the flaw and the deployment of the patch, during which these transfers could occur. Docker addressed the immediate threat by deactivating the affected tokens, but the operational recovery required a forensic analysis to ensure that no unauthorized actions had been taken using these transferred credentials.

Post-Remediation Credential Management

Following the remediation, Docker has overhauled the credential management architecture to enforce strict ownership controls and auditability. The platform now requires consent from a user before they are named as an organization owner, ensuring that credential transfers are intentional and authorized. Additionally, Docker is recording an auditable history of every token ownership change, which provides a clear trail of administrative actions. This change is critical for operational security, as it allows administrators to track who holds which credentials and when changes occurred. By implementing these controls, Docker aims to prevent similar issues in future administrative workflows and provide users with greater confidence in the security of their authentication tokens.

Operational Impact

Impact on Administrators and Engineers

The recent vulnerability in Docker Hub’s identity and access management, tracked as CVE-2026-105445, introduced a critical exposure window that required immediate technical intervention from administrators and engineers. The flaw allowed personal access tokens (PATs) to be transferred to a new owner during account-to-organization conversions without the consent of the user who originally created the token. This occurred from August 26, 2024, until the issue was remediated on September 30, 2026. For system administrators, the primary concern was the potential compromise of CI/CD pipelines and deployment workflows that relied on these tokens. Engineers managing container registries had to verify that no malicious actors had leveraged the transferred tokens to inject code or tamper with image repositories. The investigation into the exposure involved correlating registry authentication logs, Docker Hub usage data, and IAM token records to enumerate every account conversion performed since the vulnerability was introduced. This process was necessary to determine the scope of the potential breach and to identify which specific tokens required deactivation.

Prerequisites and Access Constraints

Rollout And Governance Decisions

The remediation process for administrators involved specific technical checks and constraints that differed based on the user's status during the exposure window. Docker Hub reviewed every account conversion back to the date the flaw was introduced and notified every user and organization owner whose account could have been impacted. For administrators of organizations that received transferred tokens, the immediate technical action was to review and revoke any unrecognized PATs. The platform deactivated the identified transferred PATs on October 8th, but this action was contingent on user consent; tokens that their owners explicitly asked to keep before the deadline were excluded from the automatic revocation. This created a constraint where administrators had to manually verify the legitimacy of tokens that were not automatically removed. Furthermore, the investigation was limited by the availability of logs; registry logs only show token usage, not existence, meaning the investigation could not definitively confirm whether transferred tokens were actually used. Consequently, administrators had to rely on usage data and static analysis of the highest-risk public images to ensure no tampering occurred, rather than relying solely on evidence of execution.

Realistic Evaluation and Governance Approach

Following the incident, Docker Hub implemented a robust governance approach to prevent recurrence and improve the security posture of credential management. One of the most significant changes is the requirement for explicit consent from a user before they are named as an organization owner. This ensures that when a token is transferred during an account conversion, the new owner is aware and has the opportunity to validate the token's legitimacy. Additionally, the platform is now recording an auditable history of every token ownership change. This allows administrators and engineers to trace the lineage of credentials and detect any anomalies in token transfer patterns. The company is also reviewing other flows that change credential ownership for the same pattern to ensure a holistic security improvement. For users who did not receive the notification email, the advisory confirmed that they and their organization members were not exposed, eliminating the need for further action. However, for those who were impacted, the new governance framework provides a clear mechanism for consent and auditability, reducing the risk of unauthorized credential transfers in future account conversions.

Failure Modes And Limits

Failure Modes and Security Implications

The recent vulnerability in Docker Hub's identity and access management (CVE-2026-105445) highlights a critical failure mode in credential lifecycle management. The flaw allowed personal access tokens (PATs) to be transferred to a new owner during account-to-organization conversions without explicit user consent. This occurred because the system enumerated account conversions and correlated them with registry authentication logs and IAM token records, yet failed to validate token ownership transfer against the new owner's intent. The exposure window spanned from August 26, 2024, to September 30, 2026, creating a significant period during which malicious actors could have exfiltrated credentials or injected malicious code into repositories under the guise of the original account holder. While Docker confirmed the report and deployed a fix within four hours, the retrospective investigation revealed that the vulnerability was not exploited, and no malware or credential harvesting was detected. However, the mere existence of this "blind spot" in the IAM logic underscores the risks associated with automated account migrations and the potential for credential leakage during administrative transitions.

Security And Privacy Considerations

The implications of this failure extend beyond the immediate technical flaw to the broader ecosystem of secret management and token handling. The investigation relied on static analysis of public images and registry logs to determine the scope of potential damage, yet it could not definitively confirm whether transferred tokens were actively used. Registry logs only record token usage, not the mere existence of a token, which leaves a gap in forensic verification. Furthermore, the incident exposed a lack of transparency regarding token ownership changes. Docker has since implemented changes to require user consent before they are named as an organization owner and to record an auditable history of every token ownership change. These steps are essential for restoring trust, but they also highlight a systemic limitation: the reliance on manual verification and retrospective auditing rather than proactive, permission-aware enforcement during the conversion process.

Verification and Environment Checklist

Open Questions

To ensure the security and integrity of your Docker Hub environment following these developments, the following checklist is recommended for production deployment:

• Audit and Revoke Tokens: Review all personal access tokens (PATs) and organization secrets. Revoke any tokens that were active during the exposure window (August 26, 2024, to September 30, 2026) or that were transferred during an account conversion without your explicit consent.
• Verify Organization Ownership: Confirm that you have been notified of any changes to organization ownership. If you were not notified but suspect an account conversion may have occurred, verify the current ownership status and revoke any unauthorized access.
• Review IAM Logs: Correlate your authentication logs with Docker Hub usage data to ensure no unauthorized pushes or pulls occurred during the exposure window.
• Update GitHub Apps and Permissions: Ensure that GitHub Apps are configured with the least privilege principle. Utilize the new offline_access scope to manage short-lived, rotating tokens and review the new repository_creation:write and installation_repositories:write permissions to ensure they are only granted where necessary.
• Test Secret Scanning Pipelines: Verify that your secret detection pipelines are functioning correctly. GitHub’s new context-aware secret classifier offers improved precision and recall, but it is important to test the integration with your specific workflow to ensure it reduces false positives and meets your security requirements.

Environment Checklist

Verification Statement

This article was not lab-tested. The information provided regarding Docker Hub's CVE-2026-105445 response and GitHub's secret detection improvements is synthesized from official vendor announcements and changelogs. Readers must verify the current status of these vulnerabilities and features directly with the respective vendors before deploying changes to production environments.