Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
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.
Wed, 11 Nov 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Quay: red hat quay: unauthenticated registry signing-key takeover via service key rotation | |
| First Time appeared |
Redhat
Redhat quay |
|
| Weaknesses | CWE-1287 | |
| CPEs | cpe:/a:redhat:quay:3 cpe:/a:redhat:quay:5 |
|
| Vendors & Products |
Redhat
Redhat quay |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-11-11T15:02:31.341Z
Reserved: 2026-11-06T10:23:55.509Z
Link: CVE-2026-123710
No data.
No data.
No data.
OpenCVE Enrichment
No data.