CVE-2026-123710

Quay: red hat quay: unauthenticated registry signing-key takeover via service key rotation

  • Critical 9.8

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.

Key facts

Published
11 Nov 2026
Last changed
13 Nov 2026
Assigned by
redhat
EPSS
0.657% likely to be exploited in the next 30 days, higher than 52.042% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 9.8CVSS 3.1, Criticalfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What to do

  • Restrict access to the /keys endpoint at the proxy or load balancer so only trusted internal components can reach it. Review audit logs for service_key_rotate and service_key_delete events with a null expiration_date, and remove any unrecognised approved service keys. Deleting a rogue key is not durable until a fixed build is deployed, because the anonymous request can install a new key.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Project Quayquay
  • Default status: unaffected
  • 0 up to but excluding 3.9.28 (affected)
  • 3.10.0 up to but excluding 3.10.28 (affected)
  • 3.12.0 up to but excluding 3.12.24 (affected)
  • 3.14.0 up to but excluding 3.14.10 (affected)
  • 3.15.0 up to but excluding 3.15.9 (affected)
  • 3.16.0 up to but excluding 3.16.7 (affected)
  • 3.17.0 up to but excluding 3.17.7 (affected)
  • 3.18.0 up to but excluding 3.18.3 (affected)
Red HatRed Hat Quay 3.10
  • Default status: affected
  • 1793993674 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.12
  • Default status: affected
  • 1793993854 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.14
  • Default status: affected
  • 1793993848 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.15
  • Default status: affected
  • 1793993771 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.16
  • Default status: affected
  • 1793993799 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.17
  • Default status: affected
  • 1793993778 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.18
  • Default status: affected
  • 1793993890 up to but excluding * (unaffected)
Red HatRed Hat Quay 3.9
  • Default status: affected
  • 1793993730 up to but excluding * (unaffected)
Red Hatmirror registry for Red Hat OpenShift 2
  • Default status: affected
Red HatRed Hat Quay 5
  • Default status: affected

Timeline

  1. 6 Nov 2026 Reported to Red Hat.
  2. 11 Nov 2026 Made public.
  3. 11 Nov 2026 Published

Weakness

References