Critical Docker Hub Flaw Exposes Supply Chain to Image Impersonation for Two Years

Docker has disclosed and patched a critical vulnerability, tracked as CVE-2026-105445, in Docker Hub that could have enabled unauthorized manipulation of container images. The flaw, which existed for over two years (from August 26, 2024, until its fix on September 30, 2026), allowed an attacker to push, pull, or delete images as another user. This was possible due to a weakness in the account conversion feature, where personal access tokens (PATs) were reassigned to a new organization owner without revoking the original token's secret or requiring consent from the named owner. This vulnerability is significant for practitioners because it directly impacts the integrity of the software supply chain. In a world increasingly reliant on containerized applications, the ability for an unauthorized party to inject malicious code or alter legitimate images within a widely used registry like Docker Hub poses a severe threat. Even though Docker reported no evidence of exploitation, the potential for such an attack could have led to widespread compromise of downstream systems and applications. Developers and DevOps teams depend on the trustworthiness of container images, and a flaw of this nature erodes that trust, necessitating a re-evaluation of image provenance and validation strategies. The broader context here is the ongoing and escalating challenge of software supply chain security. As organizations embrace microservices and cloud-native architectures, the reliance on third-party components and public registries grows. This trend, while enabling rapid development, also introduces new attack vectors. Recent years have seen numerous incidents highlighting vulnerabilities in dependencies, build processes, and distribution channels. Docker's swift remediation of this particular flaw is commendable, but it serves as a stark reminder that even foundational platforms are not immune. The industry continues to grapple with establishing robust security frameworks that encompass every stage of the software delivery pipeline, from code inception to deployment. In practice, this means that while Docker has addressed the immediate vulnerability on Docker Hub itself (meaning no user-side update is required), practitioners must remain proactive. It reinforces the importance of implementing image scanning tools, verifying image signatures, and maintaining strict access controls for registry interactions. Teams should also consider adopting a "least privilege" approach for PATs, limiting their scope and lifespan. Furthermore, for critical applications, exploring private registries or enhanced image attestation mechanisms can add additional layers of defense against similar supply chain attacks. This event should prompt a review of existing security policies and a renewed focus on end-to-end supply chain integrity.