{"id":"CVE-2026-123710","kind":"vulnerability","aliases":["CVE-2026-123710"],"related":[],"title":"Red Hat Quay: unauthenticated clients can install signing keys and access private images","description":"A flaw was found 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. Registry tokens signed with that key are accepted for any repository, allowing read and write access to private images and replacement of repository tags.","summary":"Red Hat Quay, a container image registry, lets an unauthenticated client obtain an anonymous registry token with an audience it controls and use it on the service key rotation endpoint to install its own signing key with no expiry. Tokens signed with that key are then accepted for any repository, giving read and write access to private images and the ability to replace repository tags.","severity":"critical","cvss":9.8,"epss":null,"exploited":false,"exploited_at":null,"products":[{"name":"Red Hat Quay","fixed":[],"affected":"3, 5 (no version ranges published)","ecosystem":"vendor"}],"ecosystems":[],"tags":["container-registry","infrastructure","red-hat-quay","self-hosted","unauthenticated"],"not_affected_if":["managed-hosting"],"how_to_check":"Check whether /keys on your Quay (service key server) is reachable by untrusted clients, e.g. through your proxy or load balancer. Review audit logs for service_key_rotate and service_key_delete events with a null expiration_date, and for approved service keys you do not recognise.","fix":"No fixed Quay build is named on Red Hat's page yet (unknown; check the Red Hat CVE page and Bugzilla 2568072). Until then restrict /keys at the proxy or load balancer to trusted internal components. Deleting a rogue key is not durable before a fixed build, since the anonymous request can install a new one.","status":"open","published_at":"2026-11-11T15:17:18+00:00","first_seen_at":"2026-11-11T15:27:49+00:00","triaged_at":"2026-11-11T15:29:40+00:00","updated_at":"2026-11-11T15:30:59+00:00","category":"infrastructure","confidence":0.7,"triage":{"at":"2026-11-11T15:29:40Z","model":"claude-haiku-5-5","output":{"fix":"unknown","reach":"internet","title":"Red Hat Quay: unauthenticated clients can install signing keys and access private images","impact":"high","summary":"Red Hat Quay, a container image registry, lets an unauthenticated client obtain an anonymous registry token with an audience it controls and use it on the service key rotation endpoint to install its own signing key with no expiry. Tokens signed with that key are then accepted for any repository, giving read and write access to private images and the ability to replace repository tags.","audience":"businesses","category":"infrastructure","nicknames":[],"who_cares":["red-hat-quay","self-hosted","container-registry"],"confidence":0.6,"fix_status":"unknown","needs_auth":"no","worst_case":"attacker reads and overwrites private images across all repositories","analyst_note":"Find affected Red Hat Quay versions, the fixed release and whether the key rotation endpoint is exposed by default, from the NVD entry and Red Hat advisories.","how_to_check":"unknown","plain_action":"","product_name":"","needs_analyst":true,"not_affected_if":["managed-hosting"],"who_is_affected":"Teams that run a self-hosted Red Hat Quay registry are exposed if the service key rotation endpoint is reachable. The sources do not name affected versions or configurations, so unknown. Teams using a hosted registry they do not operate can skip this.","user_interaction":"no","product_ecosystem":"","needs_special_setup":"unknown","severity_if_unknown":"critical"},"cost_usd":0.000709,"input_tokens":4545,"output_tokens":509,"severity_before":"critical"},"analyst_status":"done","analyst_note":"Find affected Red Hat Quay versions, the fixed release and whether the key rotation endpoint is exposed by default, from the NVD entry and Red Hat advisories.","search":"'-123710':16A,19A '-2026':15A,18A 'abil':95B 'accept':81B,148C 'access':11A,89B,156C 'allow':152C 'anonym':48B,114C 'approv':135C 'audienc':53B,119C 'client':5A,45B,110C 'contain':24B,39B 'container-registri':23B 'control':55B,121C 'cve':14A,17A 'endpoint':64B,130C 'expiri':73B,140C 'flaw':101C 'found':103C 'give':85B 'hat':2A,21A,29B,36B,106C 'host':33B 'imag':13A,40B,92B,159C 'infrastructur':26B 'instal':7A,66B,132C 'key':9A,62B,70B,78B,128C,137C,146C 'let':42B 'obtain':46B,112C 'present':122C 'privat':12A,91B,158C 'quay':3A,22A,30B,37B,107C 'read':86B,153C 'red':1A,20A,28B,35B,105C 'red-hat-quay':27B 'registri':25B,41B,49B,115C,141C 'replac':97B,161C 'repositori':84B,98B,151C,163C 'rotat':63B,129C 'self':32B 'self-host':31B 'servic':61B,127C 'sign':8A,69B,75B,136C,143C 'tag':99B,164C 'token':50B,74B,116C,124C,142C 'unauthent':4A,34B,44B,109C 'use':57B 'write':88B,155C","nicknames":[],"mitigations":[],"who_affected":"Teams running self-hosted Red Hat Quay (NVD lists Quay 3 and Quay 5 as affected) are exposed where the /keys endpoint is reachable by untrusted clients. Anyone who can get an anonymous token from /v2/auth can install a signing key and read or write any private repository. Teams on a registry they do not operate, or with /keys limited to internal components, can skip it.","tier":"B","verified":{"how_to_check":{"at":"2026-11-11T15:30:59Z","by":"analyst","doc":"https://access.redhat.com/security/cve/CVE-2026-123710","run_id":3562},"who_affected":{"at":"2026-11-11T15:30:59Z","by":"analyst","doc":"https://access.redhat.com/security/cve/CVE-2026-123710","run_id":3562}},"analyst_revisit_at":null,"fix_status":"none","audience":"businesses","plain_action":null,"pkeys":["hatquay","redhatquay"],"ptokens":["hat","quay","red"],"labels":["containerregistry","critical","infrastructure","redhatquay","selfhosted","unauthenticated"],"campaign_type":null,"search_a":"'-123710':16A,19A '-2026':15A,18A 'access':11A 'client':5A 'cve':14A,17A 'hat':2A,21A 'imag':13A 'instal':7A 'key':9A 'privat':12A 'quay':3A,22A 'red':1A,20A 'sign':8A 'unauthent':4A","search_b":"'abil':95B 'accept':81B 'access':89B 'anonym':48B 'audienc':53B 'client':45B 'contain':24B,39B 'container-registri':23B 'control':55B 'endpoint':64B 'expiri':73B 'give':85B 'hat':29B,36B 'host':33B 'imag':40B,92B 'infrastructur':26B 'instal':66B 'key':62B,70B,78B 'let':42B 'obtain':46B 'privat':91B 'quay':30B,37B 'read':86B 'red':28B,35B 'red-hat-quay':27B 'registri':25B,41B,49B 'replac':97B 'repositori':84B,98B 'rotat':63B 'self':32B 'self-host':31B 'servic':61B 'sign':69B,75B 'tag':99B 'token':50B,74B 'unauthent':34B,44B 'use':57B 'write':88B","search_c":"'accept':148C 'access':156C 'allow':152C 'anonym':114C 'approv':135C 'audienc':119C 'client':110C 'control':121C 'endpoint':130C 'expiri':140C 'flaw':101C 'found':103C 'hat':106C 'imag':159C 'instal':132C 'key':128C,137C,146C 'obtain':112C 'present':122C 'privat':158C 'quay':107C 'read':153C 'red':105C 'registri':115C,141C 'replac':161C 'repositori':151C,163C 'rotat':129C 'servic':127C 'sign':136C,143C 'tag':164C 'token':116C,124C,142C 'unauthent':109C 'write':155C","cause_entry":null,"cause_path":null,"disclosures_checked_at":null,"first_public_at":"2026-11-11T15:17:18+00:00","kev":null,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","cvss_by":"secalert@redhat.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-123710","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-123710","severity":null,"published_at":"2026-11-11T15:17:18+00:00","modified_at":"2026-11-11T15:17:18+00:00","first_seen_at":"2026-11-11T15:27:49+00:00","fetched_at":"2026-11-11T15:27:49+00:00","note":null},{"source":"analyst","external_id":"CVE-2026-123710:3562","url":"https://access.redhat.com/security/cve/CVE-2026-123710","severity":null,"published_at":"2026-11-11T15:30:59+00:00","modified_at":"2026-11-11T15:30:59+00:00","first_seen_at":"2026-11-11T15:30:59+00:00","fetched_at":"2026-11-11T15:30:59+00:00","note":"Red Hat CVE page read: Quay 3 and 5 listed affected on NVD; no fixed version published yet; mitigation is to restrict /keys at proxy. Not exploited per sources; no PoC found.","cites":["https://access.redhat.com/security/cve/CVE-2026-123710","https://access.redhat.com/security/cve/CVE-2026-123710","https://nvd.nist.gov/vuln/detail/CVE-2026-123710"]}],"documents":[{"id":126638,"url":"https://access.redhat.com/security/cve/CVE-2026-123710","title":"Red Hat CVE-2026-123710","kind":"advisory","source":"analyst","publisher":null,"text":null,"published_at":null,"relation":"advisory","confidence":null,"note":null},{"id":126638,"url":"https://access.redhat.com/security/cve/CVE-2026-123710","title":"Red Hat CVE-2026-123710","kind":"advisory","source":"analyst","publisher":null,"text":null,"published_at":null,"relation":"mitigation","confidence":null,"note":null},{"id":126639,"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-123710","title":"NVD CVE-2026-123710","kind":"other","source":"analyst","publisher":null,"text":null,"published_at":null,"relation":"describes","confidence":null,"note":null}],"disclosures":[],"exploit_sources":[],"notice":"Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai"}