Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Red Hat Quay Signing Key Takeover (CVE-2026-123710)

CVE-2026-123710 is a critical Red Hat Quay flaw that lets an unauthenticated client take over registry token signing.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-123710
Vendor
Red Hat
Affected Product
Red Hat Quay
Exploitation
Not confirmed
Published
2026-11-11

Red Hat says the client can install an approved signing key that does not expire.Tokens signed with that key can grant access to any repository, including private images. Red Hat assigns a preliminary CVSS 3.1 score of 9.8 Critical.

What it allows

How Does CVE-2026-123710 Affect Red Hat Quay?

Red Hat says the key rotation service checks whether a token has a valid signature, audience, and issuer. It does not verify that the token is specifically authorized for key rotation.

An unauthenticated client can therefore use an anonymous registry token to add its own approved signing key. The key may have no expiry, allowing the client to create tokens that Quay accepts across repositories.

Those tokens can permit reading and writing private images and replacing repository tags. This makes the flaw a serious registry integrity and confidentiality risk, particularly for images used in software delivery.

Brandefense Blackhole recorded two posts about CVE-2026-123710 between August 13 and November 11, 2026, one on Discord and one on Telegram. These are discussion counts, not evidence that the flaw has been exploited.

CISA KEV catalog version 2026.11.10 did not list this CVE. The available Red Hat and NVD records do not establish exploitation in the wild.

Who is affected

Which Red Hat Quay Deployments Need Attention?

Red Hat identifies deployments whose key rotation service is reachable by untrusted clients as affected. Its cited CVE page does not give a version range or identify a fixed release.

Inventory the paths by which outside clients can reach Quay and review access to the key rotation service. Use the vulnerability management guide to coordinate the inventory and follow-up.

Teams that distribute images through Quay should assess the integrity of sensitive repositories and tags. A compromised registry may create a software supply chain concern, although the cited record does not describe a downstream incident.

What Should Defenders Do First?

Red Hat recommends restricting access to the key rotation service at a proxy or load balancer so only trusted internal components can reach it. It also recommends reviewing service key rotation and deletion audit events for keys without an expiry.

Remove any unrecognized approved service keys after investigation. Red Hat warns that deletion alone is not durable before a fixed build is deployed, because a client can install another key.

Track the vendor advisory for a fixed build and validate the deployed version when one becomes available. The vulnerability prioritization entry can help teams weigh exposed Quay services against other work.

Tip: Keep the access restriction in placeRed Hat says removing an unrecognized key is not durable until a fixed build is deployed. Restrict access to the key rotation service while investigating.

Timeline

  1. 2026-11-11

    NVD published the Red Hat CNA description and preliminary CVSS 3.1 score for CVE-2026-123710.

What to do

  1. Restrict key rotation service access

    Limit access at the proxy or load balancer to trusted internal components, as Red Hat recommends. Verify the restriction from an untrusted network position.

  2. Review signing key audit events

    Review service key rotation and deletion events for keys with a null expiration date. Investigate any unrecognized approved service key before removing it.

  3. Plan a durable fix

    Monitor Red Hat's CVE page for a fixed build and deploy it when available. Red Hat warns that removing a rogue key alone does not prevent reinstallation.

  4. Assess repository integrity

    Brandefense recommends reviewing sensitive image access and unexpected tag changes. Red Hat says forged registry tokens can read and write private images and replace tags.

What Brandefense can do

Frequently Asked Questions

What is CVE-2026-123710?

It is a Red Hat Quay signing key takeover flaw. An unauthenticated client may add an approved key and mint registry tokens accepted across repositories.

Who is exposed to CVE-2026-123710?

Red Hat identifies Quay deployments whose key rotation service is reachable by untrusted clients. Its cited CVE page gives no affected version range.

Can CVE-2026-123710 affect private container images?

Yes. Red Hat says tokens signed with an attacker controlled approved key can permit reading and writing private images and replacing repository tags.

Is CVE-2026-123710 known to be exploited?

The cited records do not establish exploitation. CISA KEV catalog version 2026.11.10 did not list the CVE; Brandefense Blackhole recorded two discussion posts.

What is the first mitigation for CVE-2026-123710?

Red Hat recommends restricting the key rotation service to trusted internal components at the proxy or load balancer. Review signing key audit events and remove unrecognized approved keys.

Sources

  1. CVE-2026-123710Red Hat
  2. CVE-2026-123710 DetailNational Vulnerability Database
  3. Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →