Red Hat Quay CVE-2026-123710 (CVSS 9.8) and CVE-2026-110697 (CVSS 9.9): unauthenticated signing-key takeover and cross-tenant robot token theft; Red Hat rates both Critical and lists fixed Quay 3 builds
Red Hat says that in Red Hat Quay 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, so registry tokens signed with that key are accepted for any repository, allowing read and write access to private images and replacement of repository tags (CVE-2026-123710, CVSS 3.1 9.8, Critical).
Red Hat says deployments where /keys is reachable by untrusted clients are affected. In a second flaw, CVE-2026-110697 (CVSS 3.1 9.9, Critical), Red Hat says the robot account listing function builds a SQL LIKE pattern from user-controlled namespace names without escaping wildcard characters, so an attacker who creates a namespace containing an underscore can retrieve robot accounts and their decrypted authentication tokens from other tenants' namespaces; Red Hat says no elevated privileges or victim interaction are required, and that where Quay is the integrated registry for OpenShift, stolen robot credentials can be used to inject malicious images into CI/CD pipelines.
Red Hat made both public on 11 November 2026 (14:00 UTC, 22:00 Perth) and credits Dave O'Connor (Red Hat). Red Hat lists the same RHSA errata, released 11 November, as fixing both flaws in Red Hat Quay 3.9, 3.10, 3.12, 3.14, 3.15, 3.16, 3.17 and 3.18; as of 16 Nov its CVE data still lists Red Hat Quay 5 and mirror registry for Red Hat OpenShift 2 as Affected. (source: Red Hat)
- Product
- Red Hat Quay container registry; mirror registry for Red Hat OpenShift
- Versions
- Red Hat lists fixes for Red Hat Quay 3.9, 3.10, 3.12, 3.14, 3.15, 3.16, 3.17 and 3.18 (RHSA errata, 11 Nov 2026); Red Hat Quay 5 and mirror registry for Red Hat OpenShift 2 listed as Affected (as of 16 Nov 2026, Red Hat CVE data)
- CVSS
- 9.8 (CVE-2026-123710) and 9.9 (CVE-2026-110697), CVSS 3.1, Red Hat; Red Hat severity: Critical
- Exploited in Australia?
- unknown
- Patch to
- Red Hat (CVE-2026-110697 guidance): 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; Red Hat says it has already fixed Quay.io. For CVE-2026-123710, Red Hat advises restricting access to the /keys endpoint at the proxy or load balancer so only trusted internal components can reach it, and reviewing audit logs for service_key_rotate and service_key_delete events with a null expiration_date, removing any unrecognised approved service keys; it says deleting a rogue key is not durable until a fixed build is deployed.
