Red Hat disclosed two critical flaws in its Quay container registry, The Hacker News reports. CVE-2026-123710 (CVSS 9.8) lets an attacker add their own signing key to the keys Quay trusts, with no expiry. Quay then accepts tokens signed with that key for any repository, so the attacker can pull private images (and any secrets baked into them) and push or overwrite images. Quay enables anonymous access by default, and with it on, no account is needed. Quay’s key server doesn’t check the token was issued for key rotation, so an anonymous token from /v2/auth passes.
The second, CVE-2026-110697 (CVSS 9.9), lets a user who can create a namespace steal other tenants’ robot account tokens through an unescaped SQL LIKE wildcard. Red Hat lists every Quay 3 and Quay 5 version as affected and released fixed builds for eight Quay 3 branches. Its guidance: block /keys at the proxy except for trusted internal parts, search audit logs for service_key_rotate and service_key_delete events with a null expiration, remove unknown service keys, and install the fix.
My take
A registry is your supply chain. If someone can overwrite images, every system that pulls them later is theirs. Patch first, then hunt for planted keys, because deleting one key doesn’t help until the fix is running.
God Bless, and Use the Source!
