Red Hat Quay CVE-2026-123710: Unauthenticated Registry Signing-Key Takeover — Patch Now

Red Hat Quay security advisory: signing-key takeover, patch now. Critical, CVSS 3.1 9.8 (CNA: Red Hat), CVE-2026-123710. Not in CISA KEV.

Red Hat has released fixed Red Hat Quay 3 builds for CVE-2026-123710, a critical flaw in self-managed Red Hat Quay container registries. According to Red Hat, an unauthenticated client can install its own approved signing key through Quay's service key rotation endpoint. It can then sign registry tokens that Quay accepts "for any repository, allowing read and write access to private images and replacement of repository tags." Red Hat, as the CNA, scores it CVSS 3.1 9.8 Critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and rates it Critical on its own severity scale. NVD lists the record as Analyzed and shows Red Hat's score as Secondary. NVD has not published its own Primary score.

Red Hat published fixed builds on 11 November 2026 for each Red Hat Quay 3 stream it lists as affected. Red Hat found the flaw itself; its CVE record credits Dave O'Connor of Red Hat. No exploitation has been reported by Red Hat or in the public sources reviewed, and CVE-2026-123710 is not in the CISA Known Exploited Vulnerabilities catalog as of this review. Organizations that run their own Red Hat Quay 3 registry should update to the fixed build for their branch now. Users of Red Hat Quay 5 or the mirror registry for Red Hat OpenShift 2, which Red Hat's CVE data lists as affected with no fixed build named, should confirm their update path with Red Hat. Until a fixed build is in place, block untrusted access to the /keys endpoint.

Technical Information

The CVE.org record is PUBLISHED by Red Hat as CNA. It was published on 11 November 2026 at 15:02:31Z (17:02 Asia/Jerusalem, UTC+2), and Red Hat's timeline gives the public date as 14:00Z (16:00 Asia/Jerusalem). The record's title is "Quay: red hat quay: unauthenticated registry signing-key takeover via service key rotation". It assigns CWE-1287 (Improper Validation of Specified Type of Input).

Red Hat's CVE page explains the cause. Key rotation checks only that the caller's token is signed by an already-approved key with the expected audience and issuer. It does not check that the token is actually a rotation credential. "An anonymous token minted by /v2/auth satisfies that check." The new key inherits approval and can be created with no expiry, "so forged registry tokens are accepted for any repository." Red Hat says: "Deployments where /keys is reachable by untrusted clients are affected."

Red Hat's solution article lists what a successful attacker could do: pull private images "along with any secrets or credentials stored in them"; push or overwrite images; keep access through a key that "survives restarts until someone removes it"; and break normal pushes and pulls by deleting the instance's own keys. Two points from that article matter for defenders:

  • Anonymous access is on by default, and with it on, no account is needed. Red Hat warns that turning anonymous access off "doesn't protect you, because any valid Quay account can still exploit the flaw."
  • Resetting passwords or regenerating robot tokens does not revoke an unauthorized signing key.

Red Hat says the exposure applies to "any Quay instance that untrusted clients can reach", including internal registries. Its article lists standalone Quay (Podman or Docker), Quay deployed by the Quay Operator on OpenShift, and the mirror registry for Red Hat OpenShift.

The upstream fix was merged into the Project Quay repository on 11 November 2026 (quay/quay #8056). The same pull request also fixes CVE-2026-110697, a separate CNA-scored 9.9 flaw that leaks robot tokens across tenants. The Red Hat errata cover both. A public technical write-up of CVE-2026-123710 exists from Ostorlab (see Sources). This advisory does not reproduce exploit steps.

Exploitation and KEV. No exploitation has been reported by Red Hat or in the public sources reviewed. CVE-2026-123710 is not in the CISA KEV catalog (JSON feed: catalogVersion 2026.11.13, checked 16 November 2026 at 09:47 Asia/Jerusalem). CISA added an SSVC assessment to the CVE record on 13 November 2026 (CISA ADP Vulnrichment, also shown on NVD): exploitation "none", automatable "yes", technical impact "total".

Affected Product Versions

The CNA record marks upstream Project Quay as affected below each fixed build listed here. It also lists the matching Red Hat Quay streams. Each fixed Red Hat Quay 3 stream has its own erratum, all issued 11 November 2026 and updated 12 November.

Product / stream Fixed build Red Hat erratum
3.18 3.18.3 RHSA-2026:99019
3.17 3.17.7 RHSA-2026:99026
3.16 3.16.7 RHSA-2026:99022
3.15 3.15.9 RHSA-2026:99023
3.14 3.14.10 RHSA-2026:99024
3.12 3.12.24 RHSA-2026:99027
3.10 3.10.28 RHSA-2026:99025
3.9 3.9.28 RHSA-2026:99021
5 No fixed build listed Red Hat's CVE data lists Red Hat Quay 5 as "Affected"
mirror registry for Red Hat OpenShift 2 No fixed build listed Red Hat's CVE data lists it as "Affected"

Red Hat's pages do not name a fixed build for Red Hat Quay 5 or the mirror registry for Red Hat OpenShift 2. Customers on either should confirm their update path with Red Hat. If your branch is not in the table, move to a fixed branch or confirm with Red Hat. The Red Hat pages reviewed do not address the hosted Quay.io service.

Workaround and Mitigation

Update. Apply the fixed build for your branch from the table above. Red Hat's errata point to its standard update instructions. Red Hat lists no fixed build for Red Hat Quay 5 or the mirror registry for Red Hat OpenShift 2; if you run either, apply the mitigation below and contact Red Hat for your update path.

Until you can update, Red Hat's official mitigation is to:

  1. Restrict access to the /keys endpoint at the proxy or load balancer, "so only trusted internal components can reach it."
  2. Review audit logs for service_key_rotate and service_key_delete events with a null expiration_date.
  3. Remove any approved service keys you do not recognize.

Red Hat warns that "deleting a rogue key is not durable until a fixed build is deployed, because the anonymous request can install a new key." Block /keys first, then clean up.

Rescana guidance: if you find an unrecognized key, treat the registry as possibly tampered with. Check recent pushes and tag changes on images your pipelines deploy, and rotate any secrets that live inside private images. Don't rely on password or robot-token resets, which Red Hat says do not revoke a rogue key.

Indicators of Compromise

Red Hat has not published IP addresses, domains, hashes or request signatures for CVE-2026-123710, and we have not invented any. The strongest evidence Red Hat describes is in your own registry: approved service keys you do not recognize, especially with no expiry, and service_key_rotate or service_key_delete audit events with a null expiration_date. Unexplained "authentication required" or "unauthorized" errors on pushes and pulls can also be a symptom, according to Red Hat.

What to Ask Your Suppliers Today

Ask software vendors, SaaS providers and managed service providers that build or ship container images:

  1. Do you run a self-managed Red Hat Quay or Project Quay registry, including the OpenShift mirror registry? If so, which branch and build?
  2. Have you applied the fixed build for your branch? Ask for the build number and date. If they run Red Hat Quay 5 or the mirror registry, which have no fixed build listed, ask what mitigation is in place.
  3. Is your /keys endpoint reachable by untrusted clients? Ask whether it is restricted at the proxy or load balancer.
  4. Have you reviewed your approved service keys and the service_key_rotate and service_key_delete audit events? Ask whether any unrecognized key was found, and if so, whether images or tags were checked.

Track incomplete answers to closure.

Need help identifying software and SaaS suppliers that run self-managed Red Hat Quay, and tracking whether they have applied the CVE-2026-123710 fix? Our team can help you prioritize them and track their answers. Talk to an expert

Sources

  • CVE.org record for CVE-2026-123710: Red Hat CNA; published 11 November 2026, 15:02:31Z (17:02 Asia/Jerusalem); updated 13 November 2026, 20:50:57Z (22:50 Asia/Jerusalem); carries a CISA ADP Vulnrichment (SSVC) entry dated 13 November 2026.
  • NVD record for CVE-2026-123710: Analyzed (last modified 13 November 2026, 21:17Z (23:17 Asia/Jerusalem)); Red Hat CVSS 3.1 9.8 listed as Secondary; no NVD Primary score; shows the CISA ADP SSVC entry.
  • Red Hat CVE page: statement, mitigation, affected products.
  • Red Hat solution 7149923: impact, environment and remediation guidance (public summary; full article requires a subscription).
  • Red Hat errata, issued 11 November 2026: RHSA-2026:99019, 99021, 99022, 99023, 99024, 99025, 99026, 99027 (linked in the table above).
  • Red Hat Bugzilla 2568072: Red Hat's public bug report for this flaw.
  • Project Quay fix, pull request #8056: merged 11 November 2026, 19:43Z (21:43 Asia/Jerusalem).
  • CISA catalog page: CVE-2026-123710 is not in the CISA KEV catalog (catalogVersion 2026.11.13).
  • Ostorlab: independent technical analysis.

Talk to an expert

Talk to Rescana about this advisory — or about how we help TPRM teams keep reviews moving.