Critical Docker Hub Vulnerability Allows Image Tampering via Stolen Access Tokens

Docker has confirmed a high‑severity flaw in its Docker Hub service, identified as CVE‑2026‑105445, that could enable malicious actors to assume the identity of legitimate users and modify container images stored in the platform. The vulnerability hinges on the misuse of personal access tokens (PATs), which are commonly employed to automate interactions with Docker Hub repositories.

According to Docker's security advisory, an attacker who obtains a victim's PAT can gain unrestricted read and write access to the affected user's repositories. This access includes the ability to pull, push, and delete images, effectively allowing the attacker to replace trusted images with compromised versions that could execute malicious code when deployed.

The issue was first reported by the cybersecurity outlet BleepingComputer, prompting Docker to investigate and release an emergency update. In its response, Docker advised all users to immediately rotate any PATs associated with Docker Hub accounts, revoke tokens that may have been exposed, and enable two‑factor authentication where possible. The company also pledged to harden token handling mechanisms to prevent similar exploitation in the future.

Docker Hub serves as the default public registry for container images, hosting millions of repositories used by developers and enterprises worldwide. Because container images are often integrated directly into production pipelines, any unauthorized alteration can propagate across a broad range of systems, potentially leading to supply‑chain attacks. Security experts note that the ease of token reuse across automated scripts makes PATs an attractive target for attackers seeking to infiltrate container workflows.

While Docker has not disclosed the exact number of accounts potentially affected, the advisory emphasizes that the vulnerability could be exploited without requiring elevated privileges beyond possession of a valid token. Users are urged to audit their token usage, limit token scopes to the minimum necessary, and monitor repository activity for unexpected changes. Industry observers suggest that the incident underscores the growing need for robust secret management and continuous security monitoring in containerized environments.

Looking ahead, Docker plans to implement additional safeguards, including stricter token expiration policies and enhanced logging of repository actions. The company also encourages the community to adopt best practices such as signing images with Notary or similar tools to verify integrity regardless of registry access controls. As container adoption continues to rise, the incident serves as a reminder that even widely trusted platforms must be vigilant against credential‑based threats.