GoHarbor Issues Urgent Patch for Harbor Flaw Allowing Full Registry Compromise
A critical security vulnerability, identified as CVE-2026-4404, has been discovered in GoHarbor's Harbor container registry. This flaw arises from the use of hardcoded default credentials, which remain active unless altered manually by an administrator.
A critical security vulnerability, identified as CVE-2026-4404, has been discovered in GoHarbor's Harbor container registry. This flaw arises from the use of hardcoded default credentials, which remain active unless altered manually by an administrator.
Harbor is an open-source, OCI-compliant registry project designed to store, sign, and manage container images. During its initial setup, Harbor deploys with a default administrator account and a publicly known password. This configuration does not enforce a password reset upon first login or during the deployment phase, leading to potential security risks.
Remote attackers can exploit this vulnerability by scanning for exposed Harbor registries and authenticating using the default credentials. Successful authentication grants attackers complete control over the Harbor registry and associated artifacts, enabling them to overwrite container images or inject malicious content.
A critical security vulnerability, identified as CVE-2026-4404, has been discovered in GoHarbor's Harbor container registry.
Compromised registries pose a significant risk to downstream systems that pull these images, leading to potential supply-chain attacks and remote code execution in connected Kubernetes clusters. Attackers can also exfiltrate sensitive images or establish persistent access within the network by creating rogue user profiles and issuing persistent API tokens.
Security teams are advised to immediately change the default administrative password in their Harbor web interfaces to secure their environments. For new deployments, operators should assign a unique, strong password within the configuration file before installation.
The Harbor development team is working on a software patch to resolve the root cause of this vulnerability. The upcoming fix aims to eliminate the use of hardcoded passwords by randomizing credentials during installation or enforcing a mandatory password creation step.
Based on reporting by GBHackers.
