Published: October 15, 2026
Author: DigitalSpying Threat Intelligence Desk
Category: Container Security & Software Supply Chain
Tags: Docker Hub, Containers, Supply Chain Security, CVE-2026-105445, GhostPat, Personal Access Tokens, CI/CD Security, Image Integrity
Executive Summary
Container registry titan Docker has addressed a critical, high-severity vulnerability lurking within Docker Hub's core Identity and Access Management (IAM) framework. Tracked as CVE-2026-105445 (CVSS 4.0 score: 9.4) and dubbed "GhostPat", the flaw stems from an incorrect privilege assignment vulnerability during personal-to-organization account conversions.
Disclosed by security researchers and confirmed by BleepingComputer, the bug allowed an active Personal Access Token (PAT) created by a converted personal account to retain administrative permissions and automatically transfer ownership to the designated organization owner without token secret revocation or lifecycle rotation. Under active exploitation, an attacker who previously possessed or intercepted the PAT could continuously pull private corporate repositories, overwrite production container images with weaponized backdoors, or delete enterprise repositories entirely.
Deep-Dive Technical Mechanics: How GhostPat Hijacks Container Supply Chains
1. The Account Conversion Workflow
Docker Hub permits individual software developers to upgrade their personal user namespaces into corporate organizational accounts. The migration workflow requires the user to specify an existing secondary Docker Hub account as the new organization’s primary administrator:
* The personal user initiates the conversion to an organization.
* The user designates an existing account (or enters new admin credentials) to take over the organizational owner role.
* Docker Hub’s backend database re-parents the namespace, transferring repositories, webhooks, and team memberships.
2. The Flaw: Unrevoked PAT Reassignment (CWE-266)
The root cause resides in Docker Hub’s identity database migration script:
* Token Persistence Across Security Boundaries: When transferring assets, the database reassigned the internal owner_id metadata of all existing active Personal Access Tokens (PATs) to the designated new organization owner account.
* Missing Token Invalidation: Crucially, the cryptographic token secret and active session hashes were never invalidated or regenerated.
* The Exploit Scenario: If a rogue insider, compromised contractor, or former project contributor previously generated a PAT on the personal account, that token seamlessly transitioned into a valid, high-privilege organizational credential. Even after the personal account was decommissioned, the attacker could authenticate against the Docker Hub Registry API (registry-1.docker.io/v2/) using the legacy token, masquerading as the new organization owner.
3. Supply Chain Blast Radius: Stealth Image Poisoning
Because Personal Access Tokens are designed for headless CI/CD automation, they bypass Multi-Factor Authentication (MFA) prompts:
* Invisible Image Tampering: Attackers possessing a valid GhostPat token could push malicious layers to existing container tags (e.g., prod-latest or v2.4.1) without generating interactive login alerts.
* Downstream Infiltration: Automated Kubernetes clusters, serverless containers (AWS ECS, Google Cloud Run), and enterprise developers pulling updated base images would ingest the backdoored container image directly into production environments, granting the adversary remote shell access behind internal firewalls.
Enterprise Supply Chain Implications
The GhostPat disclosure underscores systemic architectural vulnerabilities across modern developer SaaS platforms:
* The Blindspot of Identity Migration: Identity migration routines often prioritize seamless workflow continuity over strict cryptographic boundary re-authentication, leaving lingering legacy access artifacts.
* Headless Token Proliferation: Organizations managing thousands of microservices frequently lose visibility into active long-lived PATs, making container registries a favored stealth entry point for initial access brokers.
Tactical Mitigations & Container Registry Hardening Playbook
Enterprise DevSecOps and cloud infrastructure teams should immediately enact the following defensive measures:
1. Audit & Rotate Docker Hub Access Tokens:
* Log into the Docker Hub organization console, navigate to Organization Settings > Personal Access Tokens, and review the issuance date and activity logs of all active tokens.
* Force an immediate revocation of all personal access tokens created prior to October 13, 2026. Reissue scoped, short-lived tokens with explicit read-only permissions where write access is not required.
2. Implement Cryptographic Image Signing & Verification:
* Deploy Docker Content Trust (DCT) or Sigstore Cosign across your CI/CD pipeline to cryptographically sign all container images at build time.
* Configure container runtime admission controllers (e.g., Kyverno, OPA Gatekeeper) in Kubernetes to reject any container image lacking a valid cryptographic signature from trusted corporate signing keys.
3. Enforce SSO & Short-Lived Ephemeral Authentication:
* Mandate Single Sign-On (SSO) and System for Cross-domain Identity Management (SCIM) provisioning across Docker Hub enterprise plans to automatically terminate tokens upon employee offboarding.
* Transition automated CI/CD runners (GitHub Actions, GitLab CI) to use OpenID Connect (OIDC) token federation instead of static long-lived Docker Hub passwords or tokens.
Sources & Further Reading:
* Docker Official Blog: Docker Hub Security Advisory CVE-2026-105445
* BleepingComputer: Docker Hub Flaw Let Attackers Impersonate Users, Tamper with Images
* Aviatrix Threat Research Center: Docker Hub Critical Flaw CVE-2026-105445 GhostPat
* SOCRadar: CVE-2026-105445: Docker Hub PAT Reassignment Flaw Analysis
* SC Media: Docker Hub Critical Vulnerability Allowed Token Misuse