CVE-2026-123710 and CVE-2026-110697, Red Hat Quay: an anonymous client can install its own registry signing key and read or overwrite every private image (CVSS 3.1 9.8), and a low-privilege account can steal other tenants' robot tokens (9.9); fixed in Quay 3.9.28 to 3.18.3, no fix for Quay 5 or the mirror registry, no exploitation reported
Red Hat Quay: anonymous signing-key takeover and cross-tenant token theft; update to your branch's fixed release
Defender actions
- Update every Red Hat Quay registry to its branch's fixed release (3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7 or 3.18.3) and, until then, restrict the /keys endpoint at the proxy or load balancer to trusted internal components; on any instance whose /keys endpoint untrusted clients could reach, review audit logs for service_key_rotate and service_key_delete events with a null expiration_date and remove unrecognised approved service keys, because deleting a rogue key is not durable before the fix and resetting passwords or regenerating robot tokens does not revoke it.
Analysis
Red Hat's record for CVE-2026-123710 says an unauthenticated client of Red Hat Quay can obtain an anonymous registry token with an audience it chooses, present it to the service-key rotation endpoint and install its own approved signing key with no expiry (Red Hat, 2026-11-11). NCSC Switzerland summarises the impact as letting network attackers with anonymous or low-privileged access read, overwrite or poison private container images and steal registry credentials, compromising the software supply chain (NCSC Switzerland, 2026-11-13). The condition is that the /keys endpoint is reachable by untrusted clients (Red Hat, 2026-11-11); anonymous access is on by default, and turning it off does not protect, because any valid Quay account can still exploit the flaw (Red Hat, 2026-11-13).
CVE-2026-110697 lets an attacker who creates a namespace containing an underscore match and retrieve robot accounts and their decrypted tokens from other tenants' namespaces; Red Hat says it needs no elevated privileges or victim interaction and that, where Quay is OpenShift's integrated registry, stolen robot credentials can inject malicious images into CI/CD pipelines (Red Hat, 2026-11-11).
Red Hat's page for the second flaw lists the fixed builds 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7 and 3.18.3 and says Quay.io is already fixed (Red Hat, 2026-11-11); its CSAF record for the first flaw links eight Quay errata, RHSA-2026:99019 and 99021 to 99027, as its fixes and lists Red Hat Quay 5 and the mirror registry for Red Hat OpenShift 2 as affected with no fix available (Red Hat, 2026-11-13). NCSC Switzerland lists the exploitation status as unknown (NCSC Switzerland, 2026-11-13).
Cited evidence
An unauthenticated client can 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.
Update to the fixed Red Hat Quay release for your version: 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7, or 3.18.3.
Sources5
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.