A critical vulnerability in Red Hat Quay, an enterprise container registry platform, has been identified that could allow unauthorized actors to gain full control over repository access. Tracked as CVE-2026-123710, the flaw carries a maximum CVSS severity score of 9.8. It specifically impacts the service responsible for managing registry token signing keys, potentially enabling attackers to read private container images, overwrite existing repository content, and maintain persistent, unauthorized access to the registry.
Red Hat has confirmed that the vulnerability stems from the service key server being accessible to untrusted clients. By exploiting weaknesses in the platform’s key rotation mechanism, an attacker can inject their own trusted signing key. Once this malicious key is established, the attacker can generate valid registry tokens that grant them read and write permissions across any repository in the affected environment, effectively bypassing standard authentication and authorization controls.
The security risk is compounded by the persistent nature of the exploit. Red Hat’s technical documentation indicates that a malicious signing key can be configured without an expiration date and will survive registry restarts. Furthermore, the rotation process intended to manage these keys can inadvertently delete legitimate instance keys, while the attacker’s injected key possesses the capability to remove any subsequent replacement keys. This can lead to a denial-of-service scenario where legitimate users are blocked from uploading or downloading images.
Red Hat has clarified that disabling anonymous access is insufficient to mitigate the risk, as the vulnerability can also be exploited by any user possessing a valid Quay account. Additionally, the company noted that standard remediation steps, such as changing user passwords or regenerating robot tokens, do not invalidate an unauthorized signing key once it has been installed.
The vulnerability was discovered by Dave O’Connor of Red Hat. While the company has not yet provided a specific version number for a patch, it confirmed that fixes for this issue, along with a separate vulnerability tracked as CVE-2026-110697, were integrated into the project’s official GitHub repository on November 11, 2026.
In the interim, Red Hat recommends that administrators restrict network access to the key-management service to prevent unauthorized interaction. Organizations are also advised to conduct thorough audits of their system logs to identify any suspicious changes to signing keys and to manually remove any unauthorized keys identified during that process. However, the company cautioned that attackers may attempt to reinstall malicious keys until a permanent fix is fully deployed and verified within the environment.





