Red Hat Quay Flaws Allow Registry-Wide Access to Every Private Container Image (CVE-2026-123710 / CVE-2026-110697)
Scope: Red Hat Quay, standalone installs, the Quay Operator on OpenShift, and the OpenShift mirror registry, across all Quay 3 branches**
Severity: Red
Red Hat disclosed two critical vulnerabilities in Quay, its container image registry platform. CVE-2026-123710, rated 9.8 on CVSS, allows an attacker who can reach a Quay registry to read and overwrite private container images across every repository in that registry, not just ones the attacker would normally have permission to touch. When Quay’s anonymous access setting is enabled, which the platform allows by default, an attacker needs no account whatsoever to exploit this; even with anonymous access disabled, any user holding a valid account can still exploit the flaw to the same effect. Red Hat noted that the underlying logic behind this flaw has existed in Quay since its very first public commit, meaning the exposure window is effectively the entire history of the project rather than something recently introduced. A second critical flaw, CVE-2026-110697, rated 9.9, was disclosed at the same time and involves cross-tenant theft of robot tokens, Quay’s automated service accounts, under different conditions. Red Hat has released fixed builds across eight Quay 3 release branches, covering standalone installations, Quay deployed through the Quay Operator on OpenShift, and the mirror registry for Red Hat OpenShift. Organisations running Red Hat Quay in any configuration must update to a fixed release today and disable anonymous access if it remains enabled, since container registries holding private images are exactly the kind of infrastructure attackers target to poison software supply chains further downstream.
The Uganda National CERT and Coordination Center (CERT.UG/CC) encourages users and administrators to review the recommendations and apply the necessary updates.