Public vulnerability disclosure

CVE-2026-123710

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

publishedCWE-1287

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.

Technical severity9.8 criticalCVSS 3.1 · CNA: redhat
Published2026-11-11Source updated 2026-11-11
Collected2026-11-111 attributed source

Fixes and workarounds

Workaround

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.

Source: CNA: redhat

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Red Hat Quay 3
Red Hat
quay/quay-rhel8
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: affected
CNA: redhat
Red Hat Quay 3
Red Hat
quay/quay-rhel9
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: affected
CNA: redhat
Red Hat Quay 5
Red Hat
quay/quay-rhel9
https://access.redhat.com/downloads/content/package-browser/
Range not reported
Other versions: affected
CNA: redhat

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 9.8
critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCNA: redhat

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide