CVE-2026-123710: Quay: red hat quay: unauthenticated registry signing-key takeover via service key rotation
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by redhat, published 2026-11-11).
Weakness: Improper Validation of Specified Type of Input
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer has no public exploit code naming this CVE. Check Exploit Observer for anything new.
Live scores
- EPSS
- 0.007
low predicted chance of attack - VEDAS
- 0.048
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Project Quay quay | before 3.9.28 from 3.10.0 before 3.10.28 from 3.12.0 before 3.12.24 from 3.14.0 before 3.14.10 from 3.15.0 before 3.15.9 from 3.16.0 before 3.16.7 from 3.17.0 before 3.17.7 from 3.18.0 before 3.18.3 | Not stated |
| Red Hat Quay 3.10 (quay/quay-rhel8) | Not stated | 1793993674 is not affected (up to *) |
| Red Hat Quay 3.12 (quay/quay-rhel8) | Not stated | 1793993854 is not affected (up to *) |
| Red Hat Quay 3.14 (quay/quay-rhel8) | Not stated | 1793993848 is not affected (up to *) |
| Red Hat Quay 3.15 (quay/quay-rhel8) | Not stated | 1793993771 is not affected (up to *) |
| Red Hat Quay 3.16 (quay/quay-rhel9) | Not stated | 1793993799 is not affected (up to *) |
| Red Hat Quay 3.17 (quay/quay-rhel9) | Not stated | 1793993778 is not affected (up to *) |
| Red Hat Quay 3.18 (quay/quay-rhel9) | Not stated | 1793993890 is not affected (up to *) |
| Red Hat Quay 3.9 (quay/quay-rhel8) | Not stated | 1793993730 is not affected (up to *) |
| Red Hat mirror registry for Red Hat OpenShift 2 (openshift/mirror-registry-rhel8) | Not stated | Not stated |
| Red Hat Quay 5 (quay/quay-rhel9) | Not stated | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7, 3.18.3.
Vendor guidance:
- RHSA-2026:99019 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99021 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99022 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99023 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99024 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99025 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99026 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99027 (vendor-advisory, x_refsource_REDHAT)
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
Advisories on this CVE
References
Vendor advisories and patches
- RHSA-2026:99019 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99021 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99022 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99023 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99024 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99025 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99026 (vendor-advisory, x_refsource_REDHAT)
- RHSA-2026:99027 (vendor-advisory, x_refsource_REDHAT)
Technical analysis and advisories
- RHBZ#2568072 (issue-tracking, x_refsource_REDHAT)
Other references
- https://access.redhat.com/security/cve/CVE-2026-123710 (vdb-entry, x_refsource_REDHAT)
- https://access.redhat.com/solutions/7149923
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners