AEGLIX News
Security researchers have identified a critical vulnerability in Red Hat Quay that allows attackers with registry access to read and overwrite private container images across all repositories. The flaw enables an attacker to insert their own trusted signing key without an expiration date, meaning tokens signed with this key can access any repository. Using these tokens, attackers can retrieve private images along with any secrets or credentials contained within them, and can also push or overwrite images. The implanted key persists through system restarts until manually removed and has the capability to delete keys used by active Quay instances, resulting in authentication failures.
Red Hat has confirmed that every version of Quay 3 and Quay 5 is impacted by both vulnerabilities. The affected deployments encompass standalone installations, Quay deployed via the Quay Operator on OpenShift, and the mirror registry for Red Hat OpenShift. By default, Quay permits anonymous access, meaning an attacker requires no account while this feature remains enabled. Even when anonymous access is disabled, any user with a valid account can still exploit the flaw. A second critical vulnerability, identified as CVE-2026-110697 with a CVSS score of 9.9, allows a Quay user who can create a namespace to steal robot account tokens from other tenants and use them to read, push, or overwrite those tenants' images.
The primary vulnerability allows an unauthenticated client to obtain an anonymous registry token with an audience it controls, present that token to the service key rotation endpoint, and install its own approved signing key with no expiry. Registry tokens signed with that key are accepted for any repository, allowing read and write access to private images and replacement of repository tags. The second flaw involves the robot account listing function constructing a SQL LIKE pattern from user-controlled namespace names without escaping wildcard metacharacters. An attacker who creates a namespace containing an underscore character can match and retrieve robot accounts and their decrypted authentication tokens from other tenants' namespaces, leading to cross-tenant credential theft and unauthorized image operations.
Red Hat released fixed builds for eight Quay 3 branches. Remediation steps include blocking the /keys endpoint at the proxy or load balancer except for trusted internal components, searching audit logs for service_key_rotate and service_key_delete events where expiration_date is null, removing unrecognized approved service keys, and installing the fixed release. These measures address both the service key planting vulnerability and the cross-tenant robot account token theft issue affecting all supported Quay versions.
Report prepared 2026-11-12 · Based on reporting from The Hacker News. Source publication date above; subsequent developments may not be reflected.