The breach isn’t the problem. The spread is. →Free Assessment

aviatrix logoAviatrix
Under Active Attack

Executive Summary

Docker fixed a critical vulnerability (CVE-2026-105445) in Docker Hub that allowed attackers to push, pull, or delete container images as other users. The flaw, dubbed GhostPat, existed for over two years from August 2024 to September 2026 and stemmed from improper handling of personal access tokens (PATs) during account-to-organization conversions. Attackers could create a token, convert their account to an organization, and designate another user as owner, thereby gaining registry access under that user's identity. While Docker found no evidence of exploitation after reviewing 304,000 pushes, the vulnerability posed significant supply chain risks by enabling malicious image publication under legitimate names.

This incident highlights the growing sophistication of supply chain attacks targeting container registries, coinciding with increased focus on software supply chain security following recent high-profile compromises and new regulatory requirements for software bill of materials tracking.

Why This Matters Now

Container registries have become prime targets for supply chain attacks, with attackers increasingly exploiting authentication flaws to distribute malicious images under trusted publisher names, making this vulnerability type critically relevant as organizations accelerate containerization.

Attack Path Analysis

Related CVEs

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

Yes, proper token ownership validation and user consent mechanisms during account conversions would have prevented this vulnerability from occurring.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

Aviatrix Zero Trust CNSF would constrain container-based lateral movement and reduce blast radius by implementing workload segmentation and egress controls that limit attacker reach across cloud environments following the Docker Hub token hijacking incident.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: While the Docker Hub account compromise would likely still occur, CNSF visibility capabilities could detect anomalous container registry activities and unauthorized image pull patterns from compromised tokens across cloud environments.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Zero Trust segmentation policies would likely constrain the scope of repository access by limiting which workloads and environments can interact with specific container registries, reducing the blast radius of hijacked credentials.

Lateral Movement

Control: East-West Traffic Security

Mitigation: East-west traffic controls would likely limit container deployment paths and restrict inter-workload communication, constraining the attacker's ability to spread malicious images across segmented environments and organizational boundaries.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Multicloud visibility controls would likely detect and constrain unauthorized command and control communications from container workloads, limiting persistent access channels across different cloud environments and regions.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Egress security policies would likely constrain data exfiltration by controlling outbound traffic from container workloads, limiting unauthorized data transfers and repository content extraction to external destinations.

Impact (Mitigations)

Despite CNSF controls reducing attack scope, residual impact could still affect workloads that successfully pulled malicious images, though blast radius would likely be constrained to specific network segments rather than enterprise-wide compromise.

Impact at a Glance

Affected Business Functions

  • Container Registry Services
  • Software Supply Chain Management
  • DevOps CI/CD Pipelines
  • Application Deployment
Operational Disruption

Estimated downtime: N/A

Financial Impact

Estimated loss: N/A

Data Exposure

Unauthorized access to private container repositories, potential for malicious image injection into legitimate namespaces, and compromise of software supply chain integrity affecting downstream users of Docker Hub images

Recommended Actions

  • • Implement Zero Trust segmentation and identity-based policies to prevent unauthorized container registry access even with compromised credentials
  • • Deploy egress security and policy enforcement to detect and block malicious container images attempting to communicate with external command and control infrastructure
  • • Establish multicloud visibility and control to monitor container deployment patterns and detect anomalous repository access or image push activities
  • • Enable threat detection and anomaly response capabilities to identify suspicious container registry operations and unauthorized PAT usage patterns
  • • Implement Kubernetes security controls to prevent compromised container images from executing with excessive privileges or accessing sensitive workloads

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Stop Advanced ThreatsFree Containment AssessmentUnder Active Attack?
Cta pattren Image